VS2008

Windows server 2003 with service packs SharePoint SP1 Visual studio 2008 SP1 MSDN documentation Office 2007 SharePoint Designer 2007 VSeWSS 1.3 SPDisposeCheck VSTO SilverLight SDK and tools for 2.0 Windows Live Tools for Visual Studio Ghost Doc Visual SVN Tortoise SVN Debug...

So, about 2 weeks ago, VSeWSS 1.3 CTP was released. All the facts are here.  So I thought I would give it a shot again, I had basically abandoned the 1.2 version, due to restrictions.  Now some of these things have been fixed, but not all of them.  I think… well, I will continue to use the Solution Generator to create List definitions, etc. that I put into my own projects.  One big problem still, you have to run it on a machine with SP on it.  I like to develop on my host OS, and depending on where...

So have you used symbols?  Of course you have, but do you know how you are using them?  Generally when a project is built in Visual Studio, a pdb file is generated, allowing you to debug the dll catching your break points etc.  So as long as you are debugging locally you are fine.  What happens in a case where, SharePoint for instance, you are remotely debugging? I mean using remote debugger to attach to processes on a remote server?  You will see that you can attach to the process w3wp.exe no problem, but then what, no symbols are found...