Hi,

I have a, maybe strange looking, question:
Is there any way to obstruct developpers to Develop and or Deploy a newer
version of a VB.NET-application?
Things should happen like this:
- Developpers develop the application
- The application is tested, and audited for the final release
- The final release is isntalled at the clients
- After that: there can not be any other new version of the software
installed on the clients, without the permission of the person doing the
audit. so the developpers shouldn't be able to make e newer version of the
software and install it. Or copy the sourcecode into a totally new
application and isntall it etc...

I don't think something like this exists, but if it would exist it would be
great for my problem here :-)

Any hints, solutions links, ... are really appreciated!

Thanks a lot in advance,
Pieter

Yes, strange question, because if you don´t trust the developers or they do
not obey the company procedures and policies... anyway:

- Developers should not install on client machines, they should lack
permissions to do that. Normally a different team or department does this
step. There are Windows policies to prevent or audit installation of
software, etc.

- You can use a source code control (SCC) system that allows you to
establish check-in/check-out policies. For example, some SCC systems don´t
allow developers to check-in code at release candidate stage unless approved
by a team leader or a manager (to avoid breaking the product). You could use
such system to prevent check-in at all or to be notified my e-mail when
someone checks-in code.

Of course nothing prevents a developer working on his workspace, bypassing
the SCC,  removing read-only flags and making a new build on his local
machine, copying it to a USB drive and walking to visit some user....

Show quoteHide quote

Pieter,

This is as old as there is development.

It is based on seperated environments.

One of the most simple formats

The developper can use his environment
The developper and tester can get to the technical testing environment
The tester can set things into the logical testing enviroment
The production boss can set things from the logical testing environment in
the production environment.

That is just done with rights on those environments.

I hope this helps,

Cor

Yes, it's called a System Administrator.  System Administrators can audit
the machines on their domains without too much trouble.

Seriously, if your users have administrative rights to their machines,
anything goes.  If they don't, they can't install squat (within reason).
Secondly, you don't have much choice when it comes to preventing developers
copying code into an application and installing it.  Really, this is a
no-brainer.  However, if only the system administrator (auditor) is allowed
to install software, then this problem won't arise.

Don't allow developers to install software is the answer in this case.


Show quoteHide quote

Team foundation server rules :)
I don't think it will be hard to implement it. You basically need to write your own team foundation project templates.

However, I don't think its a proper solution...

  I have a, maybe strange looking, question:
  Is there any way to obstruct developpers to Develop and or Deploy a newer
  version of a VB.NET-application?
  Things should happen like this:
  - Developpers develop the application
  - The application is tested, and audited for the final release
  - The final release is isntalled at the clients
  - After that: there can not be any other new version of the software
  installed on the clients, without the permission of the person doing the
  audit. so the developpers shouldn't be able to make e newer version of the
  software and install it. Or copy the sourcecode into a totally new
  application and isntall it etc...

  I don't think something like this exists, but if it would exist it would be
  great for my problem here :-)

  Any hints, solutions links, ... are really appreciated!

  Thanks a lot in advance,
  Pieter

DraguVaso wrote:

Have you thought about having your clients run it from a virtual server
rather than installing in (thin client scenario) ... this way the only copy
is the one that can be had from the server ... you don't install it
locally.

Alternatively, I think there is now an equivalent in .NET of the Java Web
Start ( where the client is sent via the Internet to the local machine ).

In addition to the other advice offered...

Using Microsoft Managed Solutions (still in the works), you will be able to
completely control what applications are delivered to the desktop.  There
will be no opportunity for a developer to make updates on the fly to their
application, even if the end users want them to.

This is causing a great deal of change within Microsoft right now, as we
"eat our own dogfood."  It is an interesting process.

http://www.microsoft.com/presspass/features/2002/may02/05-03valentineqa.mspx

Quote: "As we roll out these next-generation management solutions, which are
long-term efforts, we believe we'll be able to provide many shorter-term
solutions for customers. For example, in the next few months we'll make
available a series of solutions that are oriented around particular
management scenarios. These solutions for management involve taking our
current products -- MOM and SMS, for instance -- and building specific
content processes, expertise and partner relationships to resolve particular
management scenarios more quickly and effectively. "

Show quoteHide quote

Wierd menu crash
Convert windows SHFILEINFO to DotNet
Beating a dead Horse: Which Language
Strange behavior
A mathematical issue
Calculating text width when printing
Accessing dlls from gac
Mysteries when clearing a data table?
Strange reference issue
Finding the leftmost pixel in a piece of text when using GDI+