You searched for the word(s): userid:50765

More Search Options

RSS Available

• Re: Web Deployment Project with custom configuration section fails to replace

  If you're saying that VS 2010 is ready for production, please tell me more . If it's (as I believed till now) in beta and not ready for production then it doesn't fit my situation. I want something that enables automation instead of getting in the way (with a partial solution) now in production . The deployment transform looks similar to something I have done internally. A specially named config for each deployment target. The implementation looks a bit like XSLT but may be a custom implementation

  Posted to Configuration and Deployment (Forum) by MikeGale on 7/29/2009

• Re: Web Deployment Project with custom configuration section fails to replace

  I have now finalised this with a report to Microsoft Connect. The bug report suggests that the feature be made to work as expected for all sections in web.config. The report is at https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=478011 If you're having the same issue you might like to go along there and add your input. My recent experience with connect has been good. They attend to your input (which admittedly takes a little time to put together) and sometimes

  Posted to Configuration and Deployment (Forum) by MikeGale on 7/28/2009

• Re: Web Deployment Project with custom configuration section fails to replace

  Nothing on this so I'm going to close it out . Looks like hand editing or writing an MSBuild task to purge XML comments are the options.

  Posted to Configuration and Deployment (Forum) by MikeGale on 7/27/2009

• Re: Implications of removing PrecompiledApp.config from an ASPX site

  Further testing suggests that the absence of the PrecompiledApp.config file stops the Global (from Global.asax) assembly from running, even though web services, compiled aspx pages etc, can operate. No exceptions seen yet. I haven't identified the exact situation to my own satisfaction but it may be something like this, to run precompiled Global: Can't have an App_Code directory Must have the PrecompiledApp.config file May need a file called App_global.asax.compiled to make it run This looks

  Posted to Configuration and Deployment (Forum) by MikeGale on 7/23/2009

• Implications of removing PrecompiledApp.config from an ASPX site

  I've been testing different methods of deploying ASP.NET (3.5) sites. I've found some behaviour I was not expecting. I'd appreciate some deeper insight if anybody here has it. Quick overview: I'm looking at mixing compile on demand and updateable/per-file/assembly pages. I've been looking at ways to move between these options. I have things in App_Code. (WCF service and code for ashx's) If I leave PrecompiledApp.config in there the site squeals that there is an App_Code directory

  Posted to Configuration and Deployment (Forum) by MikeGale on 7/23/2009
  Filed under: Deployment, compilation deployment, Asp .net 3.5

• Re: Implications of removing PrecompiledApp.config from an ASPX site

  I'm still hoping for some feedback, but I'm going to wrap this up now. I tested an alternate scenario. This works from initial testing and appears more flexible. Characteristics are: Global.asax is not precompiled but present as source. No PrecompiledApp.config file. App_Code directory may be present if desired. Pages, services and HTTP handlers are compiled into single updateabale asemblies. This configuration has both global and other code working. It offers other promises of flexibility

  Posted to Configuration and Deployment (Forum) by MikeGale on 7/23/2009

• Web Deployment Project with custom configuration section fails to replace

  I am using the feature of Web Deployment Projects (MSBuild) to replace sections of the web.config file in ASP.NET applications. This works (Though it messes with whitespace.) for standard sections in the XML. I've tried to use it for a custom configuration section , defined by a third party assembly. I get a message that the section doesn't exist: ... web.config(1): error WDP00002: missing section .... Capitalisation is correct and the XPath definition is correct. After a lot of looking I

  Posted to Configuration and Deployment (Forum) by MikeGale on 7/21/2009
  Filed under: appSettings, Web.config file, Web Application

• Re: Problem debugging classic ASP with VS 2008 SP1

  Here's a link to something about enabling stop http://support.microsoft.com/kb/269827 The usual warnings about registry editing and "retired products" apply.

  Posted to Visual Studio 2008 (Forum) by MikeGale on 2/17/2009

• Re: Problem debugging classic ASP with VS 2008 SP1

  I can understand your pain if it's not working. Unfortunately I'm on Win 2003 running IIS 6 at present, with a w3p. Your comment makes me think that behaves differently from your setup, so I can't do more. Hopefully somebody else will chip in. (I guess you've done this repeatedly. In that case ignore what follows. I'd check in my web site setup that all those debug settings are switched on etc. etc. Also maybe research what would make stop fail.)

  Posted to Visual Studio 2008 (Forum) by MikeGale on 2/17/2009

• Re: Problem debugging classic ASP with VS 2008 SP1

  Hi. I had this whole thing working in some way. I don't do it often and last time I came to do it I couldn't be bothered to figure it all out again. I was looking at VBScript in ASP. I put in a few stop commands and did it that way. Used more than one debugger VS 2008, etc. (Trivial point: I have an impression that I preferred the look of the code display in one of the other debuggers.) When I ran it I mostly had VS 2008 fired up already so debugger instatiation was quick.

  Posted to Visual Studio 2008 (Forum) by MikeGale on 2/17/2009