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

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/re...g/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

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/re...g/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

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/re...g/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

Coleen,

By using this one instead of the full conversion, things go mostly easier,

http://msdn.microsoft.com/asp.net/re...p/default.aspx

I hope this helps,

Cor

"Coleen" <(E-Mail Removed)> schreef in bericht
news:eAu$%(E-Mail Removed)...
> 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
>
>

Thanks to both of you fro your responses.

A couple of questions, if you don't mind...

First - if I understand you correctly Cor, we need to download Microsoft
Visual Studio 2005 - Update to Support Web Application Projects and then our
conversions will work better?

As for running in 2003 and re-writing in 2005, while that is possible in the
new project we are beginning (although I have done a LOT of web page
development - there is virtually no code-behind yet. It is just set up as a
demo set of screens right now) but the other project is fully functional in
2003, and very large. There is no way we can just re-write this
application, so we are going to have to bite the bullet and figure out how
to convert it.

The major problem we have is that one of our user controls has two classes
in it, and the "extra" class was moved to the App_Code directory - but only
the definitions were moved - none of the code was moved - that was all
remmed out! Any suggestions on how to convert this - or will the download
work?

Thanks again for your help,

Coleen

"Cor Ligthert [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Coleen,
>
> By using this one instead of the full conversion, things go mostly easier,
>
>
http://msdn.microsoft.com/asp.net/re...p/default.aspx
>
> I hope this helps,
>
> Cor
>
> "Coleen" <(E-Mail Removed)> schreef in bericht
> news:eAu$%(E-Mail Removed)...
> > 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
> >
> >
>
>

Coleen,

Yes you have to download it and to install. It goes than direct in Visual
Studio.

I can not prove it is going better, but with this it is handled as it was in
version 1.1 and there is much less conversion.

Cor

"Coleen" <(E-Mail Removed)> schreef in bericht
news:%(E-Mail Removed)...
> Thanks to both of you fro your responses.
>
> A couple of questions, if you don't mind...
>
> First - if I understand you correctly Cor, we need to download Microsoft
> Visual Studio 2005 - Update to Support Web Application Projects and then
> our
> conversions will work better?
>
> As for running in 2003 and re-writing in 2005, while that is possible in
> the
> new project we are beginning (although I have done a LOT of web page
> development - there is virtually no code-behind yet. It is just set up as
> a
> demo set of screens right now) but the other project is fully functional
> in
> 2003, and very large. There is no way we can just re-write this
> application, so we are going to have to bite the bullet and figure out how
> to convert it.
>
> The major problem we have is that one of our user controls has two classes
> in it, and the "extra" class was moved to the App_Code directory - but
> only
> the definitions were moved - none of the code was moved - that was all
> remmed out! Any suggestions on how to convert this - or will the download
> work?
>
> Thanks again for your help,
>
> Coleen
>
> "Cor Ligthert [MVP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Coleen,
>>
>> By using this one instead of the full conversion, things go mostly
>> easier,
>>
>>
> http://msdn.microsoft.com/asp.net/re...p/default.aspx
>>
>> I hope this helps,
>>
>> Cor
>>
>> "Coleen" <(E-Mail Removed)> schreef in bericht
>> news:eAu$%(E-Mail Removed)...
>> > 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
>> >
>> >
>>
>>
>
>

Thank you! We will do that and hope it works better!

"Cor Ligthert [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Coleen,
>
> Yes you have to download it and to install. It goes than direct in Visual
> Studio.
>
> I can not prove it is going better, but with this it is handled as it was
in
> version 1.1 and there is much less conversion.
>
> Cor
>
> "Coleen" <(E-Mail Removed)> schreef in bericht
> news:%(E-Mail Removed)...
> > Thanks to both of you fro your responses.
> >
> > A couple of questions, if you don't mind...
> >
> > First - if I understand you correctly Cor, we need to download Microsoft
> > Visual Studio 2005 - Update to Support Web Application Projects and then
> > our
> > conversions will work better?
> >
> > As for running in 2003 and re-writing in 2005, while that is possible in
> > the
> > new project we are beginning (although I have done a LOT of web page
> > development - there is virtually no code-behind yet. It is just set up
as
> > a
> > demo set of screens right now) but the other project is fully functional
> > in
> > 2003, and very large. There is no way we can just re-write this
> > application, so we are going to have to bite the bullet and figure out
how
> > to convert it.
> >
> > The major problem we have is that one of our user controls has two
classes
> > in it, and the "extra" class was moved to the App_Code directory - but
> > only
> > the definitions were moved - none of the code was moved - that was all
> > remmed out! Any suggestions on how to convert this - or will the
download
> > work?
> >
> > Thanks again for your help,
> >
> > Coleen
> >
> > "Cor Ligthert [MVP]" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> Coleen,
> >>
> >> By using this one instead of the full conversion, things go mostly
> >> easier,
> >>
> >>
> >
http://msdn.microsoft.com/asp.net/re...p/default.aspx
> >>
> >> I hope this helps,
> >>
> >> Cor
> >>
> >> "Coleen" <(E-Mail Removed)> schreef in bericht
> >> news:eAu$%(E-Mail Removed)...
> >> > 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
> >> >
> >> >
> >>
> >>
> >
> >
>
>