SA Developer .NET

Has anyone had any experience doing this?  I've been asked if it's possible, from ASP.NET 2.0 / VS 2005.

---

Unscrambling Eggs: Decompiling ASP.NET

I am assuming downgrading a project ? To my knowledge it can only be done if there is no references to ASP.Net 2.0 features like master pages, membership providers, or data providers. The solution file itself will need to be recreated and each code file added to the new solution in VS 2003. If you can compile it once done it should be fine.

---

Supplying the masses with useless information since 1996

The views, comments and opinions expressed in this post is that of the poster alone unless otherwise indicated

Diago.co.za

My biggest issues will be SqlDataSource and master pages, the former which can be done quite easily with data access code, and the latter with a frameset.  I never liked the master page thing anyway, and I've deliberately steered clear of any 'fancy' code.  It's all capture and display stuff. 

---

Unscrambling Eggs: Decompiling ASP.NET

ProfK:

My biggest issues will be SqlDataSource and master pages, the former which can be done quite easily with data access code, and the latter with a frameset.  I never liked the master page thing anyway, and I've deliberately steered clear of any 'fancy' code.  It's all capture and display stuff. 

Careful you may just start a holy war among some of us hardcore web developers with regards to master pages and framesets :). The SqlDataSource is probably going to be the most work to convert however.

---

Supplying the masses with useless information since 1996

The views, comments and opinions expressed in this post is that of the poster alone unless otherwise indicated

Diago.co.za

Diago:

The SqlDataSource is probably going to be the most work to convert however.

Not really.  They all are select only and use stored procs.  Just a lot of copy and paste.

---

Unscrambling Eggs: Decompiling ASP.NET