I heard it before but never looked at it: the MSDN magazines are also available as handy .chm files!
Check it out: http://msdn.microsoft.com/msdnmag/htmlhelp.aspx
UPDATE: This issue is confirmed by Microsoft. See this weblog entry for more information.
I have WS SP2 + .Net 2.0 framework, with WSS running on .Net 2.0. Everything works fine. Until I have a unghosted page... when I try to add a web part using the web interface I get the following exception:
Invalid postback or callback argument. Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.
I have the enableEventValidation set to false, as configured using the command:
stsadm.exe –o upgrade –forceupgrade –url http://URLOftheVirtualServer
I tried to add this setting to other web.config's and to the machine.config, but to no avail.
Seems like the SharePoint safe mode parser (executed on unghosted apsx pages) is behaving different from the normal ASP.NET page rendere.
When I modify the pages using FrontPage there is no problem.
Any ideas? I would hate to go back to the 1.1 FrameWork, because now I can write my web parts using SonOfSmartPart and the full functionality of the ASP.NET 2.0 framework.
I know I shouldn't unghost pages, but I'm doing a lot of Data View web parts.
[I'm cross-posting between my weblog (http://weblogs.asp.net/soever) and the sharepointdisussions group @ yahoo]
I must say I was amazed that when I downloaded the latest Windows SharePoint Services 2.0 Administrators Guide I only got 404 errors on every page in the contents. I downloaded the file another time, to no avail. I gave up and thought: well, the file must be corrupted. But no: this is one more step by Microsoft to provide us ultimate security!
I stumbled across this blog entry by Mark Kruger that provided the solution:
1. Right-click the CHM file, and then click Properties. 2. Click Unblock. 3. Double-click the .chm file to open the file.
One of our youngest collegues becomes a patterns&practices champion!! A smart guy with a bright future!! See his blog at http://bloggingabout.net/blogs/olaf/default.aspx. See the e-mail below!
Congratulations to this community's newest "patterns & practices Champions!" Congratulations to this community's newest "patterns & practices Champions!"(2/3/2006 3:36:58 PM) The p&p Champion award is given on a quarterly(ish) basis to members of our community who have gone "above and beyond" the call of duty with regard to helping their fellow community members. These are the people who answer questions, create useful samples or build extensions to the application blocks. In short, these are the people who really make the patterns & practices program work and we couldn't do it without them!
The award winners for February 2006 for the Enterprise Library community are:
* Olaf Conijn (OlafC). While Olaf worked on the development team for Enterprise Library for .NET 2.0, this award is for his independent contributions to the community, in particular his Environmental Overrides plug-in.
* Alois Kraus (akraus2): Alois has been one of the most active members of the Enterprise Library Community, and has provided many community members with assistance in using the new January 2006 release on message boards and via his blog.
* Francois Tanguay (FrancoisTanguay). Francois provided the Enterprise Library team and the community with some great feedback on Preview releases of Enterprise Library for .NET 2.0, and shared his own blocks and extensions with fellow community members.
Congratulations to the winners and our thanks to everyone (winner or not!) for your contributions to the community. More information about the p&p Champions program, the winners' accomplishments and winners from other communities are published on MSDN.
Posted By tomhollander