Programming with .NET - General

Re: Re: Debugging info

philsal — Sat, 04 Jul 2009 22:23:03 GMT

I was actually talking about the wcf server component. Anyway I figured out you needed to upload the program database. Thanks

Re: Re: Debugging info

SharpGIS — Thu, 02 Jul 2009 15:30:47 GMT

Clearing your browser history will have absolutely no effect. Don't you mean your browser cache?

Re: Debugging info

nirav_2052003 — Thu, 02 Jul 2009 06:45:48 GMT

Hi, You can debug your silverlight application using the same way the last post suggests, but addition to that you also have to make sure that the xap file in production is the same version as it exists in your development environment. If both xap files are not same then build your silverlight application again and copy that xap on production. Now Delete the browser history. If you do not delete your browser history, you may not be able to debug. So do that and follow the steps given in previous post.

Regards,

Nirav

Re: Debugging info

SharpGIS — Thu, 02 Jul 2009 02:41:29 GMT

Silverlight does not run on the server, but on the client. You should be able to just open your project in visual studio, then open the app in the browser from the server (don't hit Run in VS!). When IE is up and running, go to the debug menu, select "attach to process" and select the IE process. You should now be able to set breakpoints in your application. However it is important that you didn't change the source files since your generated the xap that is residing on your production server.

Debugging info

philsal — Thu, 02 Jul 2009 02:23:30 GMT

I'm trying to get the line numbers of exceptions that occur on my web server. I have a couple of elusive bugs that only occur in production. I have tried using the system.diagnostics.stacktrace to get the line numbers (this works in vs2005) but the line numbers are always 0 on my production server.

Any ideas?