View Edwin Vriethoff's profile on LinkedIn

This product requires ASP.NET v2.0 to be set to ‘Allow’ in the list of Internet Information Services (IIS) Web Server Extensions

January 29, 2008   11:38


This product requires ASP.NET v2.0I’m currently performing a migration process and during the Moss installation the following error message is presented:

“This product requires ASP.NET v2.0 to be set to ‘Allow’ in the list of Internet Information Services (IIS) Web Server Extensions. If it is not available in the list, re-install ASP.NET v2.0.”

But on my machine Visual Studio 2005 and .NET2 are installed, so that’s a bit strange. Checking out the IIS extensions panel is indeed not showing the v2.0 version.

To solve the issue open your command prompt en navigate to:
%drive%\Windows\Microsoft.NET\Framework\v2.0.nnnnn
where nnnnn is the least significant version number of ASP.NET 2.0.

Now run the following command at the command prompt:
“aspnet_regiis.exe -iru -enable”
and the issue should be fixed.

Source: Office online - Windows SharePoint Services 2.0 IT Documentation

Tags: , , , , , .





InfoPath IXMLDOMDocument: Reference to undeclared namespace prefix

October 30, 2007   12:00


InfoPath IXMLDOMDocument Reference to undeclared namespace prefixBy making use of the Microsoft Office Interop libraries it is possible to fill an InfoPath form automatically. This can be useful when you would like to run a large batch of initial settings.

Trying to set a query property in the DOM of a data source I received the error “Reference to undeclared namespace prefix: ‘tns’”. The reason of this error is that the xml contains multiple namespaces and that you have to explicitly define the namespace to use.

By default the DOM property you can access from the XDocument are of the type IXMLDOMDocument. But working with this type, does not allow you to set the required namespace for your selections. To get around the issue convert the IXMLDOMDocument to a IXMLDOMDocument2 which makes it possible to define a “SelectionNamespaces” property. If you fill this property with the required documentElement’s namespace, the xpath selection of your node will succeed and the error is gone.

Below is an example of the Data source’s IXMLDOMDocument2 content (xml) and some demo code to select the required node.

(more…)

Tags: , , , , , , .









The content expressed in this blog are those of Edwin Vriethoff and do not represent his employer's view in anyway. The contents of this blog has been carefully put together, but Edwin Vriethoff is not responsible in any way for any direct or indirect harm caused by individuals or organizations using the content of this blog in any way.