Problem with IIS/ASPNET Versioning on two servers

[Guest]

I have a web application that was originally in VS2003 which was recently
converted to VS2005. It uses a 3rd party control OPControl (from omnipotent
software), which has its own web-site that you install on the server.

When I did a test deploy of my application and added it to IIS, I changed
the ASP.NET version to 2.0 and all was well. It seemed to interact quite
nicely with the OPControl site (which was still running under V1.0). I do
have them in separate application pools.

Then I went to deploy the same thing on our production server and although
my application runs, the interaction with the OPControls doesn't work
properly. In trying to figure out the differences between the one server to
the other (why one works on the other doesn't) I have found the following
slight differences.

Here's what aspnet_regiis looks like on my test server (which works):


C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -lv
1.1.4322.0 Valid (Root)
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll
2.0.50727.0 Valid
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -lk
W3SVC/ 1.1.4322.2407
W3SVC/1/ROOT/FrameworkConsole/ 2.0.50727.0
W3SVC/1/ROOT/OTISWeb/ 2.0.50727.0
W3SVC/1/ROOT/Reports/ 2.0.50727.0
W3SVC/1/ROOT/ReportServer/ 2.0.50727.0

You can see the OPControls doesn't show up... I don't know why... but it
does work. It's ASP.NET setting is V1.1



Here's what aspnet_regiis looks like on my production server (which doesn't
works):

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -lv
1.1.4322.0 Valid (Root)
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll
2.0.50727.0 Valid
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -lk
W3SVC/ 1.1.4322.2300
W3SVC/1/ROOT/ 1.1.4322.2300
W3SVC/1/ROOT/FrameworkConsole/ 1.1.4322.2300
W3SVC/1/ROOT/OPControls/ 1.1.4322.2300
W3SVC/1/ROOT/OTISWeb/ 1.1.4322.2300
W3SVC/1/ROOT/Lena/ 2.0.50727.0

Here OPControls shows up... and the Lena application listed here under
ASP.NET 2.0 is my new web-application... which is the same as the one under
the test server as OTISWeb. The OTISWeb on this server is my previous
version.

Some of my questions are:
- Do you think the slight difference in ASP.NET build numbers are
significant? (i.e.: 1.1.4322.2407 test server versus 1.1.4322.2300
production server)

- Are there any security issues that I need to be aware of that would cause
the production server (Lena) application .NET 2.0 to not interact with
OPControls .NET 1.1 and wouldn't cause any issues to be logged in the
application, security or system log?

Wondering if there anyone that can point me in the right direction for
resolving this. By the way, it appears the original OPControl vendor is no
longer in business... but try to concentrate on the fact that one
installation works with it and just really trying to figure out the subtle
difference that is keeping the other server from working.

Thanks,
Lena

 

[Guest]

Found my problem. It had nothing to do with the differing versions. A new
item showed up in my web.config file after conversion to aspnet 2.0 and I
inadvertantly didn't propogate this. The lack of this causing my 3rd party
control to fail.

<xhtmlConformance mode="Legacy"/>