.Net Website

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • CC CC

    #1

    .Net Website

    I am new to the .Net framework and have run across an interesting
    development issue and was wondering is someone has run across this before or
    had some solution ideas.

    The problem is this.

    Currently our entire website is done as on project within Visual Studio.
    The code is updated from a Source Safe Database for version control.

    We have multiple developers working on multiple updates at the same time.
    We run into problems when we package the the files into .MSI files for
    installation.

    1.) If you let the Deployment project add all Content files and Project
    files, then the Content files that have not been approved yet go out.

    We currently only add the specific files that need to go out. Is there a
    better solution?

    2.) Also, we update the code behind pages but don't want the DLL's to be
    updated until we have approval, but we still need to go live with other
    parts of the website.

    Is there a solution for this also ?

    We are planning on separating out all pages that use code behind pages in
    separate projects and including or not including the projects based on
    approval.

    Just curious to see how other companies are doing it and to see if anyone
    has some options they could recommend.

    Thanks in advance,

    Jonathan Pitcher

Working...