Re: Continue to get the license error in VS2008 even with a valid Developer License

  •  12-24-2009, 12:36 PM

    Re: Continue to get the license error in VS2008 even with a valid Developer License

    I took all of the files in the downloaded folder "Web" from CuteSoft and made a project out of them. 
     
    I get the same notice inside Visual Studio that I did before, however, it runs your project fine on my local machine.
     
    When I publish the web to our production test server, I wind up getting a server error that I am unfamiliar with.  It has to do with the added HTTPModule.
     
    Here is the error generated:  We are running IIS 7.0.  Thoughts? 
     
    Error Summary

    HTTP Error 500.22 - Internal Server Error

    An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

    Detailed Error Information
    Module ConfigurationValidationModule
    Notification BeginRequest
    Handler StaticFile
    Error Code 0x80070032
    Requested URL http://test.dynawebs.biz:80/
    Physical Path D:\Virtual Web Folders\fcweb\TEST SITE
    Logon Method Not yet determined
    Logon User Not yet determined
    Most likely causes:
    • This application defines configuration in the system.web/httpModules section.
    Things you can try:
    • Migrate the configuration to the system.webServer/modules section. You can do so manually or by using AppCmd from the command line - for example, %SystemRoot%\system32\inetsrv\appcmd migrate config "Default Web Site/". Using AppCmd to migrate your application will enable it to work in Integrated mode, and continue to work in Classic mode and on previous versions of IIS.
    • If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.
    • Alternatively, switch the application to a Classic mode application pool - for example, %SystemRoot%\system32\inetsrv\appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool". Only do this if you are unable to migrate your application.
    (Set "Default Web Site" and "Classic .NET AppPool" to your application path and application pool name)

    Matt
View Complete Thread