May 18, 2012 at 3:58 PM
Edited May 18, 2012 at 4:52 PM
This is using Silverlight 5.
This is a bit of a long shot but, we're seeing some whacky differences between our development environments (Visual Studio 2010 sp1) and our integration test servers (Server 2008 r2).
Currently we've had at least 2 occurrences where everything runs fine in dev, but there are runtime errors on the test server. 99% of the time our deployments to our test server have been working fine (for months) and we use it regularly
for client review/acceptance testing.
In one case we had to set IsKeepAlive to true when subscribing to events.
In Dev, if we didn't, the app still ran fine. No errors and everything worked correctly. There were some cases before this where even in dev we would see run time errors when IsKeepAlive was not set to true so we started always setting IsKeepAlive
to true. But in this case, in dev it worked, only on the test server did it kill the app at runtime. This was a nightmare to track down as it would show as simply as a top level object composition failure. The event subscription was many
Imports deep. Once we set the one value of IsKeepAlive on the one event things were fine again. And yes, we have hundreds of other events (all set to IsKeepAlive = true for Silverlight).
Yesterday and today I've been facing a similar problem where it runs fine in Dev but gets run-time composition errors on the test server.
I'm currently debugging it so I have no idea what the problem will be this time.
However, my question here is what suggestions does anyone have that can help me make sure my development environment matches my server environment so I can debug and solve these problems in development, not after promoting to our test servers.
My biggest issue is the only way I can debug the test servers is to make code changes (usually commenting out Imports in one file at a time) then building the solution, deploying to the test server, running it, waiting for failure, then reviewing the log
This is a horrible way to try and solve a problem.
All suggestions are welcome from trying to fix the environments to better ways to debug on a server.