469,604 Members | 2,381 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,604 developers. It's quick & easy.

Building webpages

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.
Aug 20 '07 #1
2 1207
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.
Aug 21 '07 #2
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.
Aug 21 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

7 posts views Thread by dow | last post: by
5 posts views Thread by Michael Landberg | last post: by
reply views Thread by xmail123 | last post: by
12 posts views Thread by scsharma | last post: by
4 posts views Thread by Matthias | last post: by
reply views Thread by guiromero | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.