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 7 2469
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" <co**********@yahoo.comschreef in bericht
news:eA***************@TK2MSFTNGP03.phx.gbl...
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]" <no************@planet.nlwrote in message
news:OX**************@TK2MSFTNGP04.phx.gbl...
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" <co**********@yahoo.comschreef in bericht
news:eA***************@TK2MSFTNGP03.phx.gbl...
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" <co**********@yahoo.comschreef in bericht
news:%2****************@TK2MSFTNGP03.phx.gbl...
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]" <no************@planet.nlwrote in message
news:OX**************@TK2MSFTNGP04.phx.gbl...
>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" <co**********@yahoo.comschreef in bericht news:eA***************@TK2MSFTNGP03.phx.gbl...
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]" <no************@planet.nlwrote in message
news:eQ**************@TK2MSFTNGP02.phx.gbl...
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" <co**********@yahoo.comschreef in bericht
news:%2****************@TK2MSFTNGP03.phx.gbl...
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]" <no************@planet.nlwrote in message
news:OX**************@TK2MSFTNGP04.phx.gbl...
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" <co**********@yahoo.comschreef in bericht
news:eA***************@TK2MSFTNGP03.phx.gbl...
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
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Andrew Ducker |
last post by:
VS 2005 uses Partial Classes to keep the designer-generated code
separate from the user-created code. Obviously VS 2003 doesn't.
However, when converting from 2003 to 2005, it doesn't split the...
|
by: Rich |
last post by:
(1) Is there a better place to pose the question below?
(2) I am starting to convert my enterprise solution from VS 2003 (.NET
v1.1.4322) to VS 2005 Professional (.NET v2.0.50727).
The entire...
|
by: Friso Wiskerke |
last post by:
Hi All,
We've got an VS.2003 ASPNET (VB) webproject which we would like to convert
to VS.2005 so that we can make use of the Master Page feature. Converting
the initial pages to 2005 is not such...
|
by: Dan Munk |
last post by:
Hello,
I have a large project exclusively made up of interfaces (several
hundred) that define the business objects used in our system. Heavy
inheritance and aggregation are used in the project....
|
by: Dennis D. |
last post by:
Having problems converting Murach's Beginning Visual Basic.net (Prince) and
Microsoft Press' Programming Visual Basic.net (Balena) examples for use in
VB.net 2005 Express. The VS conversion wizard...
|
by: Blasting Cap |
last post by:
I had a copy of a project that was working in Visual Studio 2003 and
Framework 1.1.
After a computer crash, I was given VS 2005 and am having more than a
little difficulty getting things to open...
|
by: Tom |
last post by:
I am converting a small VB.NET 2003 application over to VS 2005. I ran
it thru the 'upgrade' wizard which prompty upgraded it without any real
issues (except some warnings). However, I did notice...
|
by: Nathan Sokalski |
last post by:
I recently converted some ASP.NET 1.1 projects of mine, created with Visual
Studio .NET 2003, to Web Application Projects in Visual Studio .NET 2005 so
that I could use ASP.NET 2.0 (All my ASP.NET...
|
by: Vadim |
last post by:
Hello,
I need to converting project that done on Visual Studio 2005 to Visual
Studio 2003.
What the best way to do this?
Vadim Vilkhov
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new...
| |