How to manage ASP.Net Web sites from TS?

fiquebem

Can you please help me answer as many of the questions below as possible? They pertain to a new TS installation and ASP.Net Web sites.

Please assume Windows 2003 Server and a recent-enough version of ASP.Net, IIS and TS.

I have TS and Windows experience, but, unfortunately, no .Net experience.

Many thanks,

S.

1. ASP.Net Questions

a. What is a valid server configuration, including test, staging and production servers?

b. How are new ASP.Net websites added to TeamSite?

c. Is a website application template (the one inside Visual Studio 2008) appropriate for each site?

d. Is each individual website in a separate solution?

e. How is a solution compiled?

i. Should IT developers checkout the entire solution to their workstation and use Visual Studio like a typical ASP.Net development process?

ii. Can marketing developers use Dreamweaver effectively?

f. How does one solve a potential problem area related to creating new folders and files in Visual Studio and then importing these new files into TeamSite?

g. Visual SourceSafe 2005

i. The Client also uses Visual SourceSafe 2005 for source control in other projects. Should any assets be stored here?

ii. Should the source code for class library projects exist outside of TeamSite?

2. Server Architecture/Deployment

a. Is the minimum set of files deployed to IIS (no *.cs, *.csproj files)

b. How are environment specific files like web.config managed?

i. For example, each web server will have its own database and possibly its own application server.

c. How is structured content maintained via FormsPublisher converted into an ASP.Net web page?

d. Servers in each environment

i. What is a good server configuration (TeamSite, IIS, App Server)

ii. How is the website deployed to IIS (local, test, staging, production)?

1. Is OpenDeploy required? Actually, I should ask, is a OD Payload/Delivery Adapter required?

iii. Use an application server? Use WCF to communicate?

RonaldV

Very complex question, I can only give you a simple answer (hire more expertise if needed, no free lunch here :-):

1. manage your content in Teamsite
2. manage your code in MS tools (source safe etc)
3. take proper care when designing the interface between these two
4. use opendeploy to deploy content to IIS
5. if you prefer, to you can use opendeploy to deploy your compiled .net code to IIS as well (from teamsite if you want), or any other file copy tool you like

Some extra advise:
1. I would always go for xml to interface between Teamsite & .net. apsx-files are the alternative but I don't like to generate aspx-code (or any other code) in teamsite. Xml si simply better for this.
2. I would always version & deploy your compiled code in/from teamsite. This way you have the option to quickly rollback any code-deploy that fails to run on the production-IIS.

Hope this helps.