Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / August 2007

Tip: Looking for answers? Try searching our database.

Building webpages

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
magic kat - 20 Aug 2007 17:05 GMT
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.
Peter Bromberg [C# MVP] - 21 Aug 2007 01:52 GMT
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
Signature

Recursion: see Recursion
site:  http://www.eggheadcafe.com
unBlog:  http://petesbloggerama.blogspot.com
BlogMetaFinder:    http://www.blogmetafinder.com

> 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
[quoted text clipped - 6 lines]
> "Web project" that started as an App -- it has designer files in it and
> everything.
Nathaniel Greene - 21 Aug 2007 19:54 GMT
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.

> 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
[quoted text clipped - 6 lines]
> "Web project" that started as an App -- it has designer files in it and
> everything.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.