• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

.Net setup in multi developer environment??

R

rtgordon

Limp Gawd
Joined
Aug 9, 2001
Messages
252
I am trying to understand best parctices around setting up a .net web environment for multiple developers and I am trying to understand which direction to take. The way I understand it, there are basically two approaches to take:

1. Develop everything under one application
Benefits
- single config files
- ability to use one bin folder for global functions/subs for all apps in the project
Drawbacks
- management troubles
- can get complicated
- ability to use one bin folder for global functions/subs

2. Separate applications by function or use (i.e. supplier mgmt app, content management app, account management app, internal utilities app, etc)
Benefits
- separation of application functionality
- nice setup for multiple developer (get the app you need from source safe, code and go)
- less complex

Drawbacks
- You need a copy of each globals dll for each app/project (my understanding)
- Need separate config files for each app

What works best in my situation? Is there a way, if i use multiple applications, (that i am missing) of creating a global dll that spans multiple applications without having to replace each dll in each project?

could we use a web service for data access?

If you don't mind, take a moment to explain what you do. If you have any questions for me that may help answer the question, please ask me. We are converting from traditional ASP to a .net 2.0 web, and I am having trouble determining the best path. Thanks for your time and help!

gordon
 
Visual Studio 2005 has a Team Edition - I dont know exactly how it does it, or if it'll meet your specific needs but might be worth looking at
 
For my question, assume that we are using team environment. I am more concerned with how we should structure the web apps (internet and intranet/cms, etc). Thanks for helping me out. :)

gordon
 
If you are doing a single web application then it is simpler to do everything as a single application in my experience. I have done this using a setup where everyone had their local copy of IIS running and we integrated the source together using Visual Source Safe and things worked just fine. The checking out of code to local repositories on each individual workstation allowed for independent development and no worries conerning when someone else needed to do a build of the application. At the end of each day we would just pull all the lates code together to a single respository, do a build, and then release that to the server.

Now, if you are working in more of a portal application where the front of the application is nothing more than an interface to get you to separate sections of business logic, then it is better to build multiple child applications to a single master application.

Make sense, or are you still lost?
 
Yeah, I follow you... our dilemma is that we are somewhere in the middle. It probably all boils down to preference. I was just wondering what is going to be easier in an environment like ours.
 
In that case, do all that you can to do some pre-planning and draw it all out on a whiteboard... If you can get things laid out up front in terms of directory structure and such, it will help you figure out what to do for each piece. I feel for you, I have been there, checked it off, got the t-shirt, and wore the thing out. ;)
 
You must log in or register to reply here.
Back
Top