Deploying SharePoint Web Parts Build with .NET 2.0

[Via Stramit] For detailed info about WSS and SPS SP2 check out this whitepaper: Service Pack 2 for Windows SharePoint Services and SharePoint Portal Server 2003.

This white paper describes features that are included in Microsoft® SharePoint® Portal Server 2003 Service Pack 2 (SP2) and Microsoft Windows® SharePoint Services Service Pack 2 (SP2). It also provides best practices and guidance about how you can architect your solutions considering the current and future versions of SharePoint Products and Technologies.

It explains to solve an issue that I ran into a couple of months ago: when you compile your web part with .NET 2.0, you can't deploy them anymore with STSADM. The whitepaper explains how to solve this, so expect a new release for the SmartPart soon. :-) (Btw, Denis has posted his whishlist for the SmartPart. Maybe you have some ideas, requests too?)

If you want to deploy Web Part packages that contain CLR version 2.0 compiled Web Part assemblies (that is, SharePoint Web Parts compiled by using the new CLR), you will need to create a *.config file for stsadm.exe that specifies the following:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup>
<supportedRuntime version="v2.0.50727" /> <!-- update the version # once .Net v2.0 is released -->
<supportedRuntime version="v1.1.4322" /> <!-- this is the version number for .Net v1.1 -->
</startup>
</configuration>

3 Comments

  • After reading the whitepaper about SP2 for WSS and SPS I have come to the conclusion that you better nog install .NET 2.0 if you are using SPS? Is that correct? I only have one virtual directory for WSS and SPS so I can not keep the SPS on .NET 1.1. And SPS on .NET 2.0 raises an error when creating a new WSS site in the sitedirectory... Should I wait for SPS SP3 or do you have a solution for this Jan? thx!



  • FYI - SPS and .NET 2.0 do not play nice. My main portals' search capabilites went down and I was getting Gather Log Errors like this:



    The address could not be found, (0x80042616 - Error in the Site Data Web Service. )



    I uninstalled 2.0 and the search feature commenced it's normal operation. I don't know if their are any other problems or fixes but I found nothing to work around that in my searches.

  • Can you elaborate on hot to implement/where the *.Config would reside?

Comments have been disabled for this content.