So part of the problem is the WSE 3.0 Configuration tool creates an
app.config file for a project created using the Visual Studio 2005 Web
Application Project Preview (Beta 2). I assume their "if" condition is
checking to see if it's a "Web Site" project and--if so--it modifies the
web.config otherwise is modifies/creates an app.config, which is obviously
useless for an ASP.NET application.
I moved the settings from the WSE 3.0 created app.config to my web.config
all most things (including tracing) seem to work. I still experience strange
behavior WRT WSE 3.0 tracing in that *sometimes* it works an sometimes it
does not.
As I know more, so will everyone.
Regards,
Michael
> I'm using the VS 2005 Web Application Project Preview (Beta 2), which can
> be
[quoted text clipped - 11 lines]
> Kindest regards,
> Michael
Howard Hoffman - 10 Apr 2006 16:49 GMT
Michael -
There's an RC release of Web App Project
(http://www.microsoft.com/downloads/details.aspx?FamilyId=8B05EE00-9554-4733-8725
-3CA89DD9BFCA&displaylang=en)
last Friday.
The app.config vs. web.config mess-ups are now fixed. Note, however, that
the VS.NET 2005 IDE / WSE3 integration won't work -- in order to modify WSE3
configuration settings (like tracing, for example), the Wizard displayed by
VS.NET's WSE Settings 3.0 doesn't completely work. You can, fortunately,
use the WSE3 Configuration Tool exe to edit your web.config just fine.
HTH,
Howard Hoffman
> So part of the problem is the WSE 3.0 Configuration tool creates an
> app.config file for a project created using the Visual Studio 2005 Web
[quoted text clipped - 29 lines]
>> Kindest regards,
>> Michael