I am working on a web based asp.net 2.0 project that began as an application 
in Visual Studio 2005.  The web site appears to work okay, but when we 
attempt to build it, we get all sorts of errors.  The answer I get from the 
developer is "don't build it".  I am not so sure this is a good idea, isn't 
that the whole idea, that building it gives us any errors that are bound to 
come haunt us somewhere down the line.

What do you think the repercussions would be if we continued to work on this 
"Web project" that started as an App -- it has designer files in it and 
everything.

Are you saying you have a "Web Site Project" that started out as a "Web 
Application Project"?  -- because from your post, it is unclear.
Peter
-- 
Recursion: see Recursion
site:  http://www.eggheadcafe.com
unBlog:  http://petesbloggerama.blogspot.com
BlogMetaFinder:    http://www.blogmetafinder.com



"magic kat" wrote:


> I am working on a web based asp.net 2.0 project that began as an application 
> in Visual Studio 2005.  The web site appears to work okay, but when we 
> attempt to build it, we get all sorts of errors.  The answer I get from the 
> developer is "don't build it".  I am not so sure this is a good idea, isn't 
> that the whole idea, that building it gives us any errors that are bound to 
> come haunt us somewhere down the line.
> 
> What do you think the repercussions would be if we continued to work on this 
> "Web project" that started as an App -- it has designer files in it and 
> everything. 
> 
> 
> 

You have what's called a mess. Ultimately you will want to build your project 
and deploy your project, because you will not copy the project. 
Now if the project started off  as a web application project (using the vs 
2k5 plugin) it should remain that way. 

Personally, i do not prefer this method - only because it requires you 
rebuild the whole project every single time a change is made which slows down 
development, however it does make deployment easier because it eliminates the 
randomly named assembly file names. 

Hope this helps. 
What ever your team decides to do you should do it as a team and the end 
goal should be to get the project to compile properly so that you can publish 
and deploy the site properly without any unseen surprises down the line. 

"magic kat" wrote:


> I am working on a web based asp.net 2.0 project that began as an application 
> in Visual Studio 2005.  The web site appears to work okay, but when we 
> attempt to build it, we get all sorts of errors.  The answer I get from the 
> developer is "don't build it".  I am not so sure this is a good idea, isn't 
> that the whole idea, that building it gives us any errors that are bound to 
> come haunt us somewhere down the line.
> 
> What do you think the repercussions would be if we continued to work on this 
> "Web project" that started as an App -- it has designer files in it and 
> everything. 
> 
> 
>