Last post Jan 11, 2006 03:30 PM by queztionmark
Dec 05, 2005 06:13 AMfirstname.lastname@example.org|LINK
Dec 05, 2005 11:17 AM|StanDav|LINK
My problem with the conversion, and I tried both converting a single project using the project file and converting an entire web site, is that it disregards the Project files and includes everything in that directory,
both files and folders, in the project. The Solution Explorer configuration/editing doesn't work! In vs2003 right-clicking on a file(OR FOLDER) you don't want in the project removes it. With vs2005 removing a file RENAMES IT! with an '.exclude' extention,
rendering it unuseable by another project. Folders, which may belong to another application or may be needed for site operations, CANNOT be removed from the project altogether.
When you build your solution, the compiler attempts to build those folders that are not part of the project, which may contain copies or older versions of files or even 3rd party apps, causing all kinds of errors. Because
of the vs2005 design deficiencies, there are no means of correcting these problems. Quite frankly I am amazed that Microsoft has released this garbage. Obviously their Beta program (something for nothing) didn't work very well.
Out of 3 projects, I was only able to convert and build only one - simply because the environment could do no damage.
Dec 05, 2005 12:14 PM|nichole@ms|LINK
Could you post an example of one of the errors?
Have you tried fully qualifying the code (type) which is causing the 'ambigious type reference' issue. ASP.NET 2.0 may have trouble distinguishing which assembly the type is now coming from.
Dec 05, 2005 01:11 PMemail@example.com|LINK
Here is the error information from one l.ine tiem, but there are several, it is referring to temp files.
Error 1 The type 'FEDXML.FEDXMLPage' exists in both 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\fedxml2005\6011a27c\f0bf7473\App_Code.ooxu_2jh.dll' and 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\fedxml2005\6011a27c\f0bf7473\assembly\dl3\63d94d35\90ad213e_c2f6c501\FEDXML.DLL' C:\Inetpub\wwwroot\FEDXML2005\VendorInvoiceList.aspx.cs 18
thanks for any help
Dec 05, 2005 01:41 PM|mbund|LINK
Stan, why don't you tell us what you really feel? :-)
As you have found, there are differences between VS03 and VS05 web projects. One important difference is you no longer need a project file to define a web project -- a web project is defined by the files and folders in the web project's root folder. This
is a result of how the ASP.NET 2.0 compiler works; you give it a root folder location and it will compile what is there.
For the majority of our users, this simplifies creating and deploying web applications.
I would recommend you re-arrange your projects so they do not co-exist in the same folder location. This will stop the ASP.NET compiler from including extra files and folders from being compiled with your web project, and will negate the need to exclude
files. For most conversions, this is a simple thing to do.
There is one technique you can use to exclude a folder from being compiled by ASP.NET 2.0. The compiler will ignore sub-folders if (1) you have opened the web project with an HTTP location and (2) it has been marked as a vdir by IIS. This is useful if you
have a complicated solution where you have many web projects being used to create a single web application.
If you have not already done so, you should review these "step by step" and "common conversion issues and solutions" white papers found at
They discuss this conversion issue, along with many others, and gives you the recommended steps and solutions to solve them.
P.S. I'm looking forward to seeing CodeMaster's reply to Nichole and see if we can help with that problem.
Dec 06, 2005 11:07 AM|StanDav|LINK
Mike, I'll tell you(all) how I really feel. I feel anger when in this forum, someone asks me "how I really feel", when I explain my problems with vs2005. I feel
anger when someone who has not read my post, points out that projects are not used in vs2005 -
they are used in VS2003, and this is a CONVERSION issue. I feel
frustration at converting my production site development environment, which had been in use for 2 years, to vs2005. Because of "apparent" design deficiencies in vs2005, I am unable to configuring my "projects". Finally, I seek answers and alternatives,
to make this work but I will not tear my site apart to accommodate vs2005. Also, I expect professional behavior in this forum, not abuse or intimidation.
Dec 06, 2005 01:35 PM|mbund|LINK
Stan, I'm sorry to have upset you. Apparently my attempt at humor was not understood.
I have re-read my post and believe it answers your issues gracefully and professionally. Like it or not, ASP.NET 2.0 and Visual Studio 2005 have changed how they handle web projects, and this forum will try to help you convert your web application if you
There is one thing the conversion white papers mention. You can run your existing VS03 web application using an application pool setup to use ASP.NET 1.x, or even run it using an application pool setup to use ASP.NET 2.0 in binary backward compatibility
I hope that helps,
Dec 06, 2005 01:54 PM|mbund|LINK
Codemaster, your error indicates you have a type
defined both in an App_Code assembly and a user bin assembly 'FEDXML.DLL' . I am not sure whether this is a conversion issue or not.
Could you check to see if that type is defined in both places? If so, and you need both types, then changing the namespace of the type in user bin assembly
may fix your problem.
Let us know if that helps.
Dec 07, 2005 02:40 AM|ScottGu|LINK
Dec 13, 2005 04:44 PM|eActivated|LINK
This is horrible!!!! - Thank you Stan, sincerely. I actually built my projects to share the folders in order to build projects that can co-exist. I can not believe the ASP.NET team has done this.
Sure it simplifies the process for the majority.. but those of us who have been able to extract the power out of the framework.. this harms us. There should be a setting at the very least to prevent this.
The compiler should be able to compile what is defined in the file - and not just the directory structure.
Dec 13, 2005 07:23 PM|ScottGu|LINK
I actually blogged last week about a new project model option we are going to make available that will enable you to use the same project-file based VS 2003-like web project model with VS 2005. You can read the post here:
Our plan right now is to have a first preview edition of it available either this Friday or early next week, and then to refresh it again in Jan/Feb. This will allow you to-do all of the project structure approaches you did with VS 2003 -- as well as add
a number of new features for you to take advantage of as well.
Hope this helps,
Jan 10, 2006 02:03 PM|queztionmark|LINK
Dave.. I agree...
I have 6 apps set up to utilize a shared app that contains, among other resources, shared user controls (50 or so) and help files. This application directory is set up as a virdir in IIS on both my dev and live server for direct access to resources such
as graphics, documents as well as said help files and, as such, the user controls are then called by tagname and source in the calling aspx files. A reference was required because I use fileshare only and did not have Frontpage extensions installed (therefore
the 'shared' virdir did not show in or compile with the referring site app without the reference).
I installed VS05 on my personal laptop to play with the conversion process and iron out the bugs. I was throwing fits until I realized that the reference to the shared app I needed in VS03 from each of my 6 individual sites was no longer needed as long as
the site was opened as 'Local IIS' - great! the virdir now shows up and everything compiles with the referring site app. I got everything to compile (with many warnings but no errors) so I thought I was on my way.
However, as I'm finding out this morning, I am now forced to use Frontpage extensions for remote access to my dev server which, in itself is causing me problems -- I've never used or configured them so I'm getting access errors trying to do it -- another
time and forum I guess. But, if I understand this correctly, now, even IF I can get the remote sites added to my solution via the extensions, the 'shared' virdir will no longer compile with the referring app?
I've read a TON from Scottgu and have the preview version of the web project conversion module loaded on my laptop. The problem I found with this, is that, altho' I can now add and/or convert an '03 web project as a web project in '05, I STILL can't create
a reference to it.
It's nice to know that I can re-write EVERY ONE of my user controls as a custom control (about 2 solid weeks of programming) but they exist as is to keep the front-end out of the back-end. Isn't that what .NET was all about?
Jan 10, 2006 02:57 PM|ScottGu|LINK
You should definitely be able to do a project to project reference from a web project to a web project if you use the VS 2005 Web Application Project option. I have a tutorial on how to-do this for a user-control library online here:
Doesn't this handle the scenario you are after?
Jan 10, 2006 03:10 PM|eActivated|LINK
I will attempt to do this on a seperate computer in the next 2 weeks. I wish I could feel comfortable with installing VS2005/.NET 2 on my dev machine- but I have been burned too many times in the past.
I will gladely share my results... being that I have over 300+ usercontrols in the 6 web projects (42 projects in all across the framework - from web, webservice, winapp, connector libraries and support libraries) alone. Fingers crossed. Still waiting
for a handful of control vendors to update their controls to net2
I hope after disecting the next version, only minor changes will need to be done. The only direct benefit I see for .NET2 is the ability precompile to the website for performance (a darn shame that is not allowed for 1.1). I already have many more conveniences
I have written into my framework for asp.net than what they offer.
Jan 10, 2006 03:18 PM|queztionmark|LINK
Hi Scott --
This looks like a definite solution. However, I think I'll wait for the release version of the migration component as, if I'm not mistaken, I will be able to open and existing project AS a web project and not have to build a new one from scratch and move
everything in (?)...
Also - I want to clarify that I read the thread correctly. If (when) I get server extension correctly configured on my dev server and can open my existing projects via http (remote), the virtual 'shared' dir pointing to my shared project dir WILL show up
as an app folder in VS but WILL NOT compile as a part of the project? This is where the problem lies currently for me and it would be great if I mis-read this and it WOULD compile.
And, why would it compile fine from local IIS but NOT from remote http? Just curious.
Jan 11, 2006 01:01 AM|ScottGu|LINK
When migrating your VS 2003 web project you'll want to follow the exact steps outlined in this tutorial:
Jan 11, 2006 01:22 AM|ScottGu|LINK
The final release of the VS 2005 Web application project will support automatically updating the project on first open. If you follow the steps in this tutorial:
http://webproject.scottgu.com/CSharp/migration/migration.aspx, though, you should be able to migrate each existing project without having to create a new one. There are a few manual
steps to follow, but in general I've found it takes people about 20 minutes to migrate their first project and 5 minutes after that for each additional one.
I'm a little confused on your comment regarding frontpage server extensions. From your comments earlier, I though you weren't using them today with VS 2003? If so, there is no need to use them with VS 2005 Web Application projects. Instead, you can open
and edit web projects off of the file-system, and then map them (and any associated vdirs you want) using IIS.
Jan 11, 2006 11:21 AM|queztionmark|LINK
Hi again Scott -
Yeh.. that probably sounded a little confusing. Sorry =o).
I am NOT currently using them but was planning to (altho' not really thrilled about the idea) in order to use the remote service -- Web Application Projects aside. I actually DO like the new model of 'folder is project' for our purposes. I have a team of
two (possibly three soon) developers sharing projects on a central dev server and the ability to just manipulate files directly in the file structure for everyone seemed kind of nice. Also, I then wouldn't have to maintain a separate project for my shared
app - I'd have direct access through the calling app. Just a little cleaner in my opinion. As I was messing with the process yesterday, this was dependant, of course, on getting the server extensions configured correctly and, I guess, now the point is moot
anyway as it seems the app wouldn't compile like it does on my local IIS. That was essentially the point I wanted to clarify -- would it, or would it NOT compile the same with remote access using server extensions as it does on local IIS.
However, I think at this point, I would rather just use the Web App Projects to get things going quicker and maybe change the app structure later on. I have looked over the migration tutorial recently. I'll go back and look back over it again. Just for giggles,
do you have any rough ETA on the release yet?
Thanks for all your info.
Jan 11, 2006 12:46 PM|queztionmark|LINK
OK.. I'm not sure if we need to move this to another thread but here goes.
I tried the manual migration process... to the letter with one base app and my shared app. Everything went fine until I tried to reload the solution AFTER making the change in your step 6 - converting them to the new Web Application Project format by copy/paste
the text from your page.
When the solution tries to load the projects, I get this error:
"Unable to read the project file 'shared.vbproj'. [z:]\shared\shared.vbproj(182, 18): The project file could not be loaded". This is for both projects -- the other is the same but makes reference to the apps dir/path and has '(190,20)'.
The first time I tried it, I got a second error, something to the effect of ".. The application is not present ... " with more text. I tried to reproduce it and did NOT get this error on the second try. The path IS correct to both project files. [z:] is a
network drive mapped to my dev server.
Thx ---- Jeff
Jan 11, 2006 02:27 PM|ScottGu|LINK
It looks like you are using VB as the language project, can you double check that for step 6 you used the GUID in the VB tutorial (and not the one in the C# tutorial)? They are actually different, and could be the cause of the problem:
If this doesn't fix it, it might be easiest for you to send me mail directly at:
firstname.lastname@example.org. That way we can walkthrough it together and get it fixed.
Jan 11, 2006 03:30 PM|queztionmark|LINK
Thx again for the quick reply and the info...
I decided to redo the whole process (verifying I was using the VB tutorial) but with the same results.
Altho' I really appreciate the offer, I don't think I'll send you the apps as I don't think you will be able to emulate my environment correctly. None of these files resides on my local machine. My solution file resides on my personal network drive [o:],
the class libraries reside on a shared network drive for our department [k:] and the projects (including 'shared') themselves reside in the application directories on the dev server [z:]. this environment is set up this way for a purpose -- we're not using
source control at the moment but resources are still shared. I'm aware of how stupid this is but we have been growing quickly and simply have not had time to get this going.
Thx again for your help. I think I'll keep an eye out for the release.