Problems with WebLauncher ASP.NET

carl.hamilton · #1 02-12-2008, 03:52 PM

I am trying to launch a build remotely using the WebLauncher project contained in the Samples folder in VBP. So far, I have run the setup.bld project to create the IIS Virtual Directory. When I try to run the WebLauncher.sln, I get the following error:

Error 1 It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. C:\Program Files\VisBuildPro6\Samples\Misc\WebLauncher\NET1.1 \Web.Config 52

I have verfied that the Virtual Directory exists in the IIS Manager and is enabled as an application. I can provide you with any additional information you may find useful in solving this issue. Thank you in advance and I look forward to hearing from you.

kinook · #2 02-12-2008, 04:22 PM

Please ZIP and send or post:
1) The info from Help | About | Install Info
2) The installed version(s) of ASP/ASP.NET and IIS
3) The .bld file
4) A build log file

Thanks.

carl.hamilton · #3 02-12-2008, 05:06 PM

1) The info from Help | About | Install Info:

Visual Build Professional 6.6
Registered to: Kinetics (1-computer license)
Windows Version: 5.2.3790.2.0
Install path: C:\Program Files\VisBuildPro6
SftTree_IX86_U_50.dll version 5.06
unins000.exe version 51.48.0.0
VisBuildCmd.exe version 6.6.0.0
VisBuildPro.exe version 6.6.0.1
VisBuildBld.dll version 6.6.0.1
VisBuildBurn.dll version 6.6.0.0
VisBuildCore.dll version 6.6.0.0
VisBuildDotNET.dll version 6.6.0.0
VisBuildExt.dll version 6.6.0.0
VisBuildLog.dll version 6.6.0.0
VisBuildMisc.dll version 6.6.0.0
VisBuildMS.dll version 6.6.0.0
VisBuildMS2.dll version 6.6.0.0
VisBuildNet.dll version 6.6.0.0
VisBuildSvr.dll version 6.6.0.0
VisBuildSvr.Interop.dll version 1.0.0.0
VisBuildVCS.dll version 6.6.0.0

2) The installed version(s) of ASP/ASP.NET and IIS

IIS v6.0
ActiveServerPages
ASP.NET v1.1.4322
ASP.NET v2.0.50727

kinook · #4 02-13-2008, 08:25 AM

Testing on Windows Server 2003 w/ VS 2003 and ASP.NET 1.1 and 2.0 installed, both versions build and run OK in my tests. I did encounter the error "Could not load type '_Default'" running the 2.0 version until I switched the virtual dir properties (ASP.NET tab) to use ASP.NET 2.0.

There are two versions of the WebLauncher sample (the one in WebLauncher is for .NET 2.0 and the one in WebLauncher\NET1.1 is for .NET 1.1). It looks like you may have navigated to http://localhost/Build/NET1.1/Default.aspx rather than http://localhost/Build/Default.aspx after building -- I did encounter the error message you indicated when doing that, which makes sense (see http://geekswithblogs.net/ranganh/ar.../25/37609.aspx). Here are some other possibilities:
http://tinyurl.com/2emvg6

carl.hamilton · #5 02-13-2008, 10:24 AM

It does appear that I have navigated to the Default.aspx under NET1.1 version. When I compile, I still get the previously stated error....

It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. C:\Program Files\VisBuildPro6\Samples\Misc\WebLauncher\NET1.1 \Web.Config
line 52

The error is pointing to line 52 of Web.config under the NET1.1 folder:

<authentication mode="Windows" />

Should this issue in the NET1.1 Web.config have an effect on the 2.0 version? I have attached a copy of that web.config under Net1.1.

Thanks

carl.hamilton · #6 02-13-2008, 10:26 AM

Sorry I missed this before. Here is the attached Web.config for Net1.1

kinook · #7 02-13-2008, 11:56 AM

Whether you register the NET 2.0 or 1.1 project, you should navigate to http://localhost/Build/Default.aspx, not http://localhost/Build/NET1.1/Default.aspx. If you register the .NET 2.0 project and then navigate to http://localhost/Build/NET1.1/Default.aspx, you will encounter the error. Don't do that (see links in my previous post).