Re: Problems with ASPNET 2.0 Applications with Validation Controls

ajk-eis — Sat, 19 Jan 2008 10:12:10 GMT

Hi Randy (and all other interested persons),

sorry I didn't continue the thread yesterday, but I was shot after having spent the better part of three days (and nights) trying to figure this out. Add to that that tmarq (Thomas thanks again) and I are a oposite ends of the world (Thomas in Redmond with a cup of coffee fresh in the morning and I hungry at the end of a long Friday in Germany) I was glad to just shoot off the short success post and go home and to bed!

Anyway I still have thoughts on this -

1. UPDATE Jan. 20, 2008 - see my next post in this thread.

2. Randy - I see no disadvantage with a VISTA developement box. I have one myself and have no quarrel with it. What you will have to do is go to your applicationHost.config and -

Make a back up copy
Delete the ColdFusion handler mapping that I listed above.
If you don't use CF anymore then delete all of the mappings that reference CF paths and you are done.
Subsite the CF App if you have one and make a "location" section for that subsite with a handlers section including the mapping that you deleted above. In fact you should be able to do that in the web.config using the syntax that Anil posted above. If you have an integrated ASPNET App as I do you will have to change the AppPool to compatible mode.
If you can subsite the ASPNET App, run it in a separate App Pool (better anyway)
For the ASPNET Subsite you can run integrated mode.

3. Optionally, if you can subsite the ASPNET App you should be able to use "remove" tags in the web.config for that subsite to delete all of the Cold Fusion Mappings in the applicationHost.config for that subsite. That's the nice thing about IIS 7 configuration.

Many, many thanks to Thomas and the other folks at MS for the prompt and "exclusive" handling of this problem.

HTH
Alle

Search results matching tag 'Cold Fusion and ASPNET on IIS 7'

Re: Problems with ASPNET 2.0 Applications with Validation Controls