06:06:14 AM
3I40D301B
Back to the original problem of getwcinivalue throwing an error reading web.config...that is unchanged.
The IIS extension handler has .rsx mapped to: Westwind.WebConnection.WebConnectionHandler,...
In web.config...
<handlers>
<add name="*.rsx_wconnect" path="*.rsx" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode" />
<!-- add name="Rigstat custom" path="*.rsx" verb="*" modules="IsapiModule" scriptProcessor="C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" preCondition="classicMode,runtimeVersionv2.0,bitness64" /-->
</handlers>
And as I said, the app continues to work well.
~bob
Hi Bob,
Hmmm... remove this block:
<compilation> <assemblies> <add assembly="System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" /> </assemblies> </compilation> <pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID" />
I think what happened here, you probably opened the project in Visual Studio and 'upgraded' it to .NET 4.0, then deployed to a machine that doesn't have .NET 4.0 on it. Alternately you can go into the project properties and reset the project to .NET 2.0.
To do this go to the site root | Properties | Build | Target Framework.
Web Connection doesn't care about the .NET version to run, but IIS will look at these settings when it stars up the Application Pool and if the version is higher than what's installed it'll bomb. FWIW, it might not be a bad idea to run .NET 4.0 on the server since there are many performance enhancements in the newer version. I wish I could move to .NET 4.0 myself for the .NET Module, but 2.0 is built into IIS 7, .NET 4.0 is still a separate install and I don't want to require it. IIS 8 will have .NET 4.5 I believe which is probably when I start moving up to that version.
VS adds several assembly references into the config file when setting the project to .NET 4.0. That'll likely work locally, just fine, but will fail if you now move the app to a machine that doesn't have .NET 4.0 installed. Hence you want to make sure you don't say 'Upgrade to .NET 4.0' in Visual Studio.
Let me if that fixes the problem - if it doesn't give me a call tomorrow and I can help you through this...
FWIW, I checked the default files that Web Connection ships and the templates it uses and it doesn't include any assembly references to this effect so this is defintitely something that happened after installation/initial configuration.
+++ Rick ---
OK. the previous message did not format correctly. Let's try again.
There must be something wrong with my web.config file. Checking IIS, the extension handler is mapped to:
Westwind.WebConnection.WebConnectionHandler,...
When attempting to edit the entry for my .rsx extension, an error is thrown.
"Could not load file or assembly 'System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"
The System cannot find the file specified or one of its dependencies.
(C:\webs\....\web.config<span class="codestring">" Line 18)
This might be unrelated to the original issue, or the other a symptom.
The web.config has this section of interest. Line 18 begins with "<add assembly=".
<system.web>
<compilation defaultLanguage="c#" debug="false">
<buildProviders>
<add extension=".wcsx" type="System.Web.Compilation.PageBuildProvider" />
<add extension=".rsx" type="System.Web.Compilation.PageBuildProvider" />
</buildProviders>
<assemblies>
<add assembly="System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
</assemblies>
</compilation>
<pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID" />
</system.web>
A search for that public key token shows it to be a MS Report Viewer (which I have never used and is probably not installed on this server.) Any reason I cannot delete the assemblies section?
~bob
Hmmm... that's odd. If there are problems in web.config usually IIS will throw an error right away and the request will never hit Web Connection. if you're seeing that look closely at the error message - it should tell you where in web.config the error is.
It kind of sounds like the you have maybe the .wc extension set up for the module and your app scriptmap set to the ISAPI extension? It's possible the .wc extension is not mapped properly.
FWIW, re: changes to admin page - I'm making those changes now.
There will also be changes in the new version that default to using the .NET module for new applications to simplify configuration making script map configuration much easier and less error prone.
So I'm curious to hear what might be causing your problem...
+++ Rick ---
Bummer. I just tried EditConfig and it has the same error. In fact, the only link that does work is the Show and Manage ISAPI Settings.
The app works without any problems.
~bob
Bob,
That request is no longer valid. There are a number of issues with this but mainly since we've removed wwDhtmlForm from Web Connection this request is no longer used. If you need to edit settings the only way to do it now is to edit through the EditConfig link.
I may add this back in in the future using a standard Web Connection form, but for the moment that feature is gone.
Still not sure why that wouldn't work though - the .config parsing should work just fine... Does the app otherwise run - which indicates that the Web.config file is valid.
+++ Rick ---
After I upgraded to v5.62, wwMaint no longer works. Perhaps it was some other change I made at the same time, but I am unable to track it down. This is the error message.
Processing Error - wwMaint~ServerStatus
Error: 1943
Message: Member DOCUMENTELEMENT does not evaluate to an object.
Code: loNode = loXml.documentElement.selectSingleNode(lcSection + "/add[@key='" + lcKey + "']")
Program: getwcinivalue
Line No: 885
Debug shows:
lcSection = WebConnectionConfiguration
lcKey = AdminPage
Here is the line in Web.Config:
<add key="AdminPage" value="/admin/Admin.asp" />
That file does exist.
~bob
