try some comma's between the ' and job and ' and title

Roney wrote:

Simply my project has to install only once.

Set an machine registry key on install and check it before install.

Roney wrote:

is there any chance to set in click once deployment

ClickOnce only simplifies the deployment from a single point, it does not solve single installation completely.

After login, you get the cookie back. Save the cookie and use it in the new request. This often contains the login info.

In my project we use a load balancer. This load balancer hides two application servers running web services that are secured using WSE 3.0. The client regularly encounters the error: WSE559: A UsernameToken with a particular nonce value can only be used once within a given time period. Our guess is that this occurs when the load balancer routes a message to server 2 only once where the rest of the messages from that client go to server 1. Is there a way to influence the nonce so that it is unique over 2 (or more) servers?

modified on Tuesday, December 2, 2008 2:39 AM

emunews wrote:

every release requires a new round of testing and deployments

The sooner you find bug, the cheaper the project becomes. Agile projects become expensive when new requirements are brought up between iterations because more attention is being paid to the working of the program. The final quality is better. So the main issue is to keep track of changes in requirements during the iterations and make sure those changes are estimated and added to your budget.

John C wrote:

Is anyone doing their main development in a vm

We are now working on two (third is being installed) dual-quad core intel vm machines with 16 programmers on XP32 machines running VS 2005 (500k+ lines projects). Apart from the disk speed (which we are now upgrading to a SAN and local striped disks for compiling) it works great.. You can easily add a new environment (just copy) when a new programmer is needed. Also working on different versions or branches of the software can be done using different VM's. The whole test environment is also build on the same ESX VM machines.