Can I convert an asp.net 1.1 website to an 2.0 site?

[mark4asp]

I have a website written in asp.net 1.1

Is it possible to convert it to asp.net 2.0

There is no solution or project file.

I'm using VS2005.

 

[Mark Rae [MVP]]

I have a website written in asp.net 1.1

Is it possible to convert it to asp.net 2.0

There is no solution or project file.

Open it in VS.NET 2005 - the Converersion Wizard will kick in...

 

[Fao, Sean]

I have a website written in asp.net 1.1

Is it possible to convert it to asp.net 2.0

There is no solution or project file.

I'm using VS2005.

The short answer is, yes, you can certainly convert a 2003 website to
2005. That said, I have not had much luck with the conversion wizard.
It's definitely a nice start, but it was always a lot of work to get
everything up and running again. It makes it a lot easier of the
original developers followed strict best practices when developing the site.

Hope that helps,

 

[mark4asp]

Open it in VS.NET 2005 - the Converersion Wizard will kick in...

I did open it with VS2005. I didn't notice the conversion wizard do
anything.

File, Open, Web Site...
or
File, Add, Existing Web Site...

Afterwards I get warnings like this:

Warning 2 'System.Configuration.ConfigurationSettings.AppSettings' is
obsolete: 'This method is obsolete, it has been replaced by
System.Configuration!System.Configuration.ConfigurationManager.AppSettin
gs' D:\websites\AspNetJobs2\site\usercontrols\NewListings.ascx 29

Error 18 'System.Web.HttpRequest.QueryString' is a 'property' but is
used like a 'method'
D:\websites\AspNetJobs2\site\password\ViewApplication.aspx 16

[for the code: intApplicationID = Request.QueryString( "id" );]


Perhaps the problem with this code is that it's just shot full of
errors and maybe it never worked in the first place? Maybe I just
downloaded bad code!, or an untested beta.

 

[Mark Rae [MVP]]

I did open it with VS2005. I didn't notice the conversion wizard do
anything.

Hmm - are you sure it hadn't already been converted...? Can you still open
it in VS.NET 2003...?

Afterwards I get warnings like this:

That's right - the Conversion Wizard won't fix your code for you...

Perhaps the problem with this code is that it's just shot full of
errors and maybe it never worked in the first place? Maybe I just
downloaded bad code!, or an untested beta.

Possibly...

 

[BigJohn]

Have done this, multiple times.

1 - create a project file using VS 2003 (open a new project, Add Existing
Item)
2 - get the VS 2003 project functioning.
3 - Open the VS 2003 project with VS 2005 and the wizard will kick in.
4 - About 80% of the needed changes will be taken care of, the rest is on
your own.

Good luck