Re: Converting .Net 2003 to .Net 2005

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

when i first began converting my more complex asp.net applications from
2003 to 2005 I kept running into problems like you describe. In the end
I bit the bullet and went through by hand and dropped my code into
newly created UserControls in the target project.

Looking at some of your problems, for instance the uc_mc_btn_footer
error you are getting is because the way asp.net 2.0 references other
UserControls has changed. You can no longer do a direct reference to
another usercontrol in your page, you have to add the <% Reference
UserControl='myUC.ascx' /> (pseudocode) in order to reference
UserControls, and then you shouldnt get the type not defined errors
anymore.

This arises another problem, when you have UserControls that need to
have a cross-reference. On this note, the "proper" thing to do is make
an interface that displays the methods/properties you need, and then
implement that interface in your UC, then when referencing UC's, use
the interface instead of the concrete usercontrol.

Here is a helpful msdn link that helped me out ALOT when converting all
of my projects:

http://msdn.microsoft.com/asp.net/reference/migration/asp2mig/default.aspx

In the end, you do have to do quite a bit of "futzing" to get all the
projects working correctly in 2005, so much so that 2 of my projects I
just decided to leave in 2003, and am now re-developing it into 2005,
mainly because these projects were sloppy in the first place and could
do with a re-design anyways, also they are very widely used
applications and I didn't want to introduce problems in the production
code as a result of the upgrade.

I hope this helps!

Sean

Coleen wrote:
Does anyone have any good detailed information on the conversion process?
We are in the process of converting 2 projects from 2003 to 2005 and have
some conversion errors that I can not find answers to. First, we have a lot
of UserControls. I am getting the error "Type uc_mc_btn_footer is not
defined." where uc_mc_btn_footer is the name of the UserControl. Also, on
almost all of our UserControls the conversion has remmed out all my code -
so now essentially, they do nothing. What is going on? Why did it do this?
Is there any resoure I can go to to find some answers on the conversion
process and how to fix these problems?

TIA, Coleen

.

Relevant Pages

  • Re: Converting .Net 2003 to .Net 2005
    ... when i first began converting my more complex asp.net applications from ... newly created UserControls in the target project. ... You can no longer do a direct reference to ... Here is a helpful msdn link that helped me out ALOT when converting all ...
    (microsoft.public.dotnet.general)
  • Re: Converting .Net 2003 to .Net 2005
    ... when i first began converting my more complex asp.net applications from ... newly created UserControls in the target project. ... You can no longer do a direct reference to ... Here is a helpful msdn link that helped me out ALOT when converting all ...
    (microsoft.public.dotnet.general)
  • Re: Pentium M differences: 1.73Ghz? 1.86? 2.0?
    ... applications faster than a 1.73 GHz cpu your claim to saving minutes ... converting 100 images would have to be proven to me. ...
    (comp.sys.laptops)
  • Re: Convert Access 2 to Access 2000
    ... there is a compile error. ... I had major problems converting from A2.0 to A97. ... and provided that reference appears above any ADO ... >> Dim ThisPlayer As Long ...
    (microsoft.public.access.conversion)
  • Error Adding MS Access Reference to VB.Net Project
    ... A reference to 'Microsoft Access 10.0 Object Library' could not be added. ... Converting the type library to a .NET assembly failed. ... I'm running Visual Studio .Net 2002. ...
    (microsoft.public.dotnet.languages.vb)