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

More Search Options

RSS Available

• Re: Install with VS2008

  Always good advice. [quote user="Juan T. Llibre"] The usual warning is still good : never install beta programs on partitions you can't afford to format ! [/quote]

  Posted to Visual Studio 2010 Beta 1 (Forum) by BradleyB on 5/22/2009

• Re: Install with VS2008

  Correct you can install both VS08 and VS2010 on the same machine. Installing VS2010 will not affect the functionality of VS08. Brad.

  Posted to Visual Studio 2010 Beta 1 (Forum) by BradleyB on 5/22/2009

• Re: Converted from 1.1 to 2.0 Web Application Project, now project compiles twice under both models

  This post explains some of the differences in the compilation models. http://forums.asp.net/p/1023499/1995873.aspx#1995873 Hope it helps, Brad

  Posted to Migrating from ASP.NET 1.x to ASP.NET 2.0 (Forum) by BradleyB on 11/25/2007

• Re: VS2005 Web Application debugging *EXTREMELY SLOW*

  Believe it or not, with WAP and yes even VS2003 only the code behind files along with other code files *.cs or *.vb are compiled into the single code behind assembly. All the .aspx, .ascx etc.. files are still dynamically compiled by ASP.Net during the http requeset. The code behind files are not being compiled twice. VS is compiling the code files into an assembly that is placed in the bin folder. Then asp.net is compiling the page based on the assembly in bin. It's a two step process. For example

  Posted to VS 2005 Web Application Projects (Forum) by BradleyB on 11/8/2007

• Re: VS2005 Web Application debugging *EXTREMELY SLOW*

  One issue you may be running into is the validation for opened pages. Web Application Projects only compiled the code behind files into an assembly. The page class will still be compiled by ASP.Net. Opened pages in the VS editor/design surface will still use the website model for validating intellisense within the page for inline code. Try closing all open documents and see if you still have the same problem. Hope this helps, Brad.

  Posted to VS 2005 Web Application Projects (Forum) by BradleyB on 11/2/2007

• Re: Can't find "Installation Folder" dialog in Web Setup project

  Hey Mfitzgerald, I checked with one of our seutp experts and here is answer I got. Hope it helps! The Installation Folder Dialog is not available in Web Setup projects. There are three workarounds depending on your scenario: Pre-configure the web server so that the Virtual Directory you are installing to already exists and points to a folder on disk. We’ll honor that location at install-time. Add a “Custom Folder” to the File System Editor and set it’s DefaultLocation to be equal to a public property

  Posted to Visual Studio 2005 (Forum) by BradleyB on 10/16/2007
  Filed under: web setup

• Re: Object reference not set to an instance of an object - Web Application Project

  How are you deploying to the webfarm? Are you using VS or some other process to push the binaries? Thanks, Brad.

  Posted to VS 2005 Web Application Projects (Forum) by BradleyB on 8/28/2007

• Re: Error when adding Content Page from Master Page in VWDExpress

  Here are a couple of commands you can use to force VS to re-initialize its templates first try: devenv /installvstemplates if it still doesn't work try: devenv /Setup Hope this helps, Brad.

  Posted to Visual Web Developer 2005 Express (Forum) by BradleyB on 2/23/2007

• Re: MSBuild integraction issue when publishing satellite assemblies

  Got it. The change I gave you before was for localized resources in the WAP project. For referenced projects you'll need. <Copy SourceFiles="@(ReferenceCopyLocalPaths)" DestinationFiles="@(ReferenceCopyLocalPaths->'$(WebProjectOutputDir)\bin\%(DestinationSubDirectory)%(Filename)%(Extension)')" SkipUnchangedFiles="true" /> So the "Microsoft.WebApplication.targets" file should have both changes to be correct. <Copy SourceFiles="@(IntermediateSatelliteAssembliesWithTargetPath)" DestinationFiles

  Posted to VS 2005 Web Application Projects (Forum) by BradleyB on 11/17/2006

• Re: MSBuild integraction issue when publishing satellite assemblies

  You can fix this problem by modifying "Microsoft.WebApplication.targets" changing the Copy SourceFiles action for IntermediateSatelliteAssembliesWithTargetPath. Before: <Copy SourceFiles="@(IntermediateSatelliteAssembliesWithTargetPath)" DestinationFolder="$(WebProjectOutputDir)\bin" SkipUnchangedFiles="true" /> After: <Copy SourceFiles="@(IntermediateSatelliteAssembliesWithTargetPath)" DestinationFiles="@(IntermediateSatelliteAssembliesWithTargetPath->'$(WebProjectOutputDir)\bin\%(Culture

  Posted to VS 2005 Web Application Projects (Forum) by BradleyB on 11/16/2006