Login  
Search All Forums
Dart Home | PowerWEB File Upload for ASP.NET | Custom Development Reply | PowerWEB File Upload for ASP.NET Topics | Forums   
AuthorForum: PowerWEB File Upload for ASP.NET
Topic: IIS 7 Web.Config
tltabor

From: NY, NY USA
Posts: 9
Member Since: 07/13/12
posted July 15, 2012 10:41 PM

I've moved the modules in Web.Config from system.web/httpModules to system.webServer/modules per
http://support.dart.com/postings?topicid=7685

How do I prevent VS from adding the modules back to system.web/httpModules?

Thank you for your help.
Tony Priest



From: Utica, NY USA
Posts: 8466
Member Since: 04/11/00
posted July 16, 2012 8:51 AM

Are you saying that VS is changing it back every time you open the designer? If so, that is not what I see. If I use the IIS APPCMD utility to migrate the web.config:

%systemroot%\system32\inetsrv\APPCMD.EXE migrate config "Default Web Site/MyWebApp"

the changes are retained even when reopen the project in the designer.

Is that not what you are seeing?
tltabor

From: NY, NY USA
Posts: 9
Member Since: 07/13/12
posted July 16, 2012 3:05 PM

That is undoubtedly the problem. I moved the modules manually.

I've read all references to appcmd on your site and googled it and am not following.

Visual studio is creating the web.config file. The recommended fix is to migrate web.config on a web server. Here are my questions:

What does migrating web.config on a web server have to do w/ Visual Studio's codegen?

I'm developing on Windows 7, Visual Studio 2010, and IIS Express. My system does have an inetsrv directory but it is empty and i find no appcmd.exe on the system.

I do have another box with IIS 7 installed. I tried to run appcmd.exe list sites on it, but it failed for insufficient permissions.

I'm obviously not following.

Thank you for your help

Tony Priest



From: Utica, NY USA
Posts: 8466
Member Since: 04/11/00
posted July 16, 2012 3:40 PM

When we originally wrote the code for FileUpload IIS7 did not exist. For convenience we wrote it so that when the control was opened in the designer we added the handlers automatically into the web.config. If you open the page in the designer and the lines are not found, we add them.

When IIS7 came out, it turned out that there were a couple more lines that needed to be added. We found out that using APPCMD to migrate the site worked fine (which it does for me). At some point we may change our code so that the correct lines are added for IIS7 but I don't know when that will be.

I have 108 files in my C:\Windows\System32\inetsrv directory, one of which is appcmd. When I run it. it adds 'FileUploadModule' and 'CallbackManagerEx' to the modules section of system.webserver. The lines we added remain where they were and do affect operation of the page.

What behavior are you seeing that is different?
tltabor

From: NY, NY USA
Posts: 9
Member Since: 07/13/12
posted July 16, 2012 4:07 PM

You're seeing appcmd on a box that has IIS 7 installed. I develop with IIS Express, with no appcmd.

I'll try to devise a workaround.

Thank you.
Tony Priest



From: Utica, NY USA
Posts: 8466
Member Since: 04/11/00
posted July 16, 2012 4:25 PM

Yeah, it's Windows 7 Ultimate. IIS is the one that came with it, I just enabled it. Maybe you need to enable more options to get access?

What happens if you just manually add the lines? All you need to do is add:

<add name="FileUploadModule" type="Dart.FileUpload.FileUploadModule,Dart.FileUpload" preCondition="managedHandler" />
      <add name="CallbackManagerEx" type="Dart.FileUpload.CallbackManager,Dart.FileUpload" preCondition="managedHandler" />

to the <system.webServer><modules> section.


Reply | PowerWEB File Upload for ASP.NET Topics | Forums   
This site is powered by PowerTCP WebServer Tool PowerTCP WebServer for ActiveX