Multiple users with VS.Net and Sourcesafe

[EmmeS]

We in the process of converting some of our classic .asp to asp.net. Currently, we are using visual interdev but will be moving to vs.net. I have a few questions:
1) You can edit/debug/test classic asp modules in vs.net. Has anyone ever had any problems with this? Or any helpful hints?
2) Everytime we check in a module from our local machine, don't we need to rebuild the .dll on the test server? If so, don't we need to install vs.net on the test server and rebuild it there? (yuk)
2) Shouldn't we make this .dll part of sourcesafe somehow? Especially, if for some reason, we need to back-off a publish.
3) Any other good advice?

Thanks, ;-)

Emme

 

[jfrost10]

Hey Emme,

Here's what we did to solve the whole dll issue:

For our alpha version of the code, we have no dll: we just added a folder called DLL to our project and put all the .vb files in there. That way, when everyone tests the project on their machines, no dll has to be reconfigured.

For our beta release, we're in the process of taking all the code that we now know works pretty well and creating dll projects for them specifically. that way, most of the dev time is complete and there won't be a tonne of changes to the dlls.

As per your question of recompiling dlls on the server, yes, that would probably be needed if you're going to be testing it off of the server. However, I know that there are command line tools (I've never used htem, GUI boy here) that you can use instead of installing a full copy of vs.net.

hth

D'Arcy