I ran into a couple of problems with Sharepoint and the 2.0 Framework the other day. None of the custom web parts I have written were working properly. in fact they wern't working at all. In the past i did all of my testing with the 2.0 Framework on a Virtual Sharepoint server, which just had a default install of Sharepoint. Our corporate Intranet is very heavily customised and includes several custom web parts [server controls actually] (written by yours truely) that were added to the template files. The biggest offender was my "TopNav" control (which renders a dynamic drop down, tabbed control based on the portal layout of the site). The TopNav was killing the portal. This didnt surprise me overmuch since its one of the more complex controls.
With the TopNav removed, the portal would render, but every other control spit out a "Object not set to an instance of an Object" error. So far, the only way I have seen to get around this is to open the projects in VS 2005 and re-compile the projects. This of course up-sizes the code to 2.0. Thats not really a bad thing, but then you are committing yourself to 2.0 at that point. Well, I guess you already did that when you installed the framework on your server. Oh well.
No comments:
Post a Comment