Sharing compiled web assemblies between developers?

[Gregory Gadow]

All done in ASP.Net 2.0 using VB...

The website I am developing has a large DLL that includes custom
MembershipUser, MembershipProvider and RoleProvider classes, several
frequently used web controls, custom base classes for Master and Page
objects, so on and so on.

All of this was done on my main dev machine, which I've also been using
to write the website. On the dev machine, the DLL references compile
Just In Time with no errors. Recently, though, one of my co-workers
started helping with the website. He's set up with VS 2005 on his
machine and we are sharing the source through Visual Source Safe, but he
can not reference the library. As a result, pages he writes that use
these objects end up with a lot of JIT errors, even though the page runs
fine when loaded through a browser from the website.

What do I need to do to get him a working copy of the DLL? And is there
any way to automate his getting it, so that when I post a new version to
the website, he will have access to that as well? This is code I do not
want to have available to others in our office (a few co-workers like to
"tinker"), so putting this in app_code would not be the best solution.

 

[Guest]

Generally what I do is add the latest build of it to the Solution Items
folder in the VS Solution, and check it in. Then other devs can get latest on
it, and set a reference in their own working solution.
Peter

 

[Gregory Gadow]

Generally what I do is add the latest build of it to the Solution Items
folder in the VS Solution, and check it in. Then other devs can get latest on
it, and set a reference in their own working solution.

I am not familiar with a specific Solution Items folder. The library is in a
separate solution in Source Safe, and the compiled DLL is in the bin folder of
the web app.

 

[Guest]

Just right-click on the Solution (very top) node in Solution Explorer and
choose "Add item".
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com

 

[Gregory Gadow]

Just right-click on the Solution (very top) node in Solution Explorer and
choose "Add item".

Pardon my missing the obvious, but add what? The DLL itself, even though it is
already in the bin folder of the project? All that did was put a copy of the DLL in
the root folder of the web app.

Gregory Gadow

 

[Guest]

if you keep the assembly in the root of the solution (not in the /bin folder)
and set a reference to it, it will be copied local into the bin folder at
build time.
You *could* set a reference to it in the bin folder but that would likely be
problematic. Generally what we do is have a separate folder that is within
the solution, say "ExternalDlls" or whatever, and you would add your
assemblies that are kept in this folder as Solution items.

When one of them is rebuilt, all you need to do is check it out, copy the
new over the old, and check it back in, and everyone on your team can get
latest and be sure of having the latest build of that assembly.

HTH
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com

Just right-click on the Solution (very top) node in Solution Explorer and
choose "Add item".

Pardon my missing the obvious, but add what? The DLL itself, even though it is
already in the bin folder of the project? All that did was put a copy of the DLL in
the root folder of the web app.

Gregory Gadow

Peter Bromberg [C# MVP] wrote:

Generally what I do is add the latest build of it to the Solution Items
folder in the VS Solution, and check it in. Then other devs can get latest on
it, and set a reference in their own working solution.

I am not familiar with a specific Solution Items folder. The library is in a
separate solution in Source Safe, and the compiled DLL is in the bin folder of
the web app.

--
Gregory Gadow
(e-mail address removed)

:

All done in ASP.Net 2.0 using VB...

The website I am developing has a large DLL that includes custom
MembershipUser, MembershipProvider and RoleProvider classes, several
frequently used web controls, custom base classes for Master and Page
objects, so on and so on.

All of this was done on my main dev machine, which I've also been using
to write the website. On the dev machine, the DLL references compile
Just In Time with no errors. Recently, though, one of my co-workers
started helping with the website. He's set up with VS 2005 on his
machine and we are sharing the source through Visual Source Safe, but he
can not reference the library. As a result, pages he writes that use
these objects end up with a lot of JIT errors, even though the page runs
fine when loaded through a browser from the website.

What do I need to do to get him a working copy of the DLL? And is there
any way to automate his getting it, so that when I post a new version to
the website, he will have access to that as well? This is code I do not
want to have available to others in our office (a few co-workers like to
"tinker"), so putting this in app_code would not be the best solution.