Search

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

Matching Posts

  • Re: how to convert a standard vs 2005 project into a web application project

    Check out this site. It has instructions on how to convert both VS2003 to VS2005 WAP and VS2005 websites to the new VS2005 WAP model. http://webproject.scottgu.com/
  • Re: What's for you the best ASP - to - ASP.NET converter?

    Here is a previous post on the subject.... You cannot convert directly from ASP to ASP 2.0. The programming models are very different. You could try to use the old tool http://msdn.microsoft.com/asp.net/using/migrating/aspmig/aspmigasst/ to convert to ASP 1.X and then open that WebSite in VS2005 to convert it to ASP 2.0, but I am not sure how successful you will be. ASP conversion white paper http://msdn.microsoft.com/asp.net/learning/learn/migratingfromasp/default.aspx Here are two white papers
  • Re: Programmatically accessing user controls

    It also sounds like you might be a canidate for the New Web Application Project Model that we are working on. This project model is similiar to the VS2003 model. Migration is much cleaner to this model. Here is Scott Gu's blog on the subject: http://weblogs.asp.net/scottgu/archive/2006/02/16/438354.aspx (Link to download at top) NOTE: We are about to release an updated version of to the WAP add-in (Web Application Project) in the next couple of days. Most issues have been addressed, but this is still
  • Re: Dynamic rendered SVG content cannot be viewed after migrating to ASP.NET 2.0

    Are you updating to the Website model (default for VS2005) or the Web Application Project model (new add-in that is current in beta)? If the website model, then did you get the update to the conversion wizard found here: http://www.microsoft.com/downloads/details.aspx?FamilyId=7CECD652-FC04-4EF8-A28A-25C5006677D8&displaylang=en
  • Re: Covert vs 2003 to 2005

    Not quite sure why you are getting this error. The format looks correct <pages> <namespaces> <add namespace ="WebApplication1"/> </namespaces> </pages> Can you tell me if you are converting to the new WebSite model in VS2005 or to the new Web Application Project model which is in Beta? If you are converting to the new WebSite model (default for VS2005), then do you have the update to the Conversion wizard? http://www.microsoft.com/downloads/details.aspx?FamilyId=7CECD652
  • Re: Programmatically accessing user controls

    I assume you are converting to the new Website model and not the pre-release of the Web Application Model (WAP) which is more like the Everett model that is out in Beta format. Before your conversion did you get the update to the Migration Wizard found here: http://www.microsoft.com/downloads/details.aspx?FamilyId=7CECD652-FC04-4EF8-A28A-25C5006677D8&displaylang=en This fixed a ton of migration issues after the final release of VS2005. Hope this helps Note: If you interested in Web Application
  • Re: Issue creating new wesite in VS2003 !!

    Did this start happening as soon as you install VS2005 Express? What happens when you uninstall VS2005 Express? Make sure that you location is still http://localhost in VS2003 when creating websites. You should be able to run these SxS without issues. You may need to use run aspnet_regiis -i to fix your script maps from the windows\microsoft.net\framework\v1.1.4322 directory. Hope this helps
  • Re: Upgrade ASP.NET 1.1 to 2.0 get this error

    Calvin, are you migrating from VS2003 to the new VS2005 website model? Do you have the update to the Migration wizard found here: http://www.microsoft.com/downloads/details.aspx?FamilyId=7CECD652-FC04-4EF8-A28A-25C5006677D8&displaylang=en
  • Re: Ways to Preserve Existing Code when Migrating?

    Your best migration experience will most likely be with the NEW Web Application Project model which is most similiar to VS2003. You can find more information here: http://weblogs.asp.net/scottgu/archive/2006/02/16/438354.aspx http://webproject.scottgu.com/Default.aspx If you do want to go to the new Web Site Model, then here is some information from a previous post I made. Here are two white papers on the subject of converting from 1.1 to 2.0: Step-By-Step Guide to Converting Web Projects from Visual
  • Re: Programmatically set culture for an entire application

    You will have to programatically modify the Web.config file yourself. There is no built in method to accomplish this. Hope this helps. To set the UI culture and culture for all pages, add a globalization section to the Web.config file, and then set the uiculture and culture attributes. <configuration> <system.web> <globalization culture="en-US" uiCulture="de-DE" /> </system.web> </configuration>
    Posted to Localization (Forum) by NHuffman on 2/28/2006
Page 1 of 7 (65 items) 1 2 3 4 5 Next > ... Last »