Comments
Sort by recent activity
Yes, you should be able to do this. Profile the Visual Studio debug instance and it will profile everything including Silverlight code. If it doesn't work get in touch with support@red-gate.com / comments
Yes, you should be able to do this. Profile the Visual Studio debug instance and it will profile everything including Silverlight code. If it doesn't work get in touch with support@red-gate.com
There are a couple of things you can try to get this working. First, switch the profiling mode from "line level" to "method level".
Second, remove any pdbs you have. If it works after this, you just need to work out which pdb is causing the problem.
If it still doesn't work after trying these. We'll need to analyse a memory dump (using a debugger like windbg) to work out exactly what the problem is. / comments
There are a couple of things you can try to get this working. First, switch the profiling mode from "line level" to "method level".
Second, remove any pdbs you have. If it works after this, you jus...
Unfortunately this doesn't give us a whole lot to go on. I assume your application works on before using smartassembly.
Are you able to at least narrow it down a little by working out which feature is causing this? Probably the best way to do this is to turn all the options off and add them one by one until you hit the problem again. / comments
Unfortunately this doesn't give us a whole lot to go on. I assume your application works on before using smartassembly.
Are you able to at least narrow it down a little by working out which feature...
I just sent you an email, Please let me know if you get it.
If you can send us a reproduction of the problem you're seeing and the saproj file you used to protect the assembly, it lets us get to the heart of the issue a lot faster [image] / comments
I just sent you an email, Please let me know if you get it.
If you can send us a reproduction of the problem you're seeing and the saproj file you used to protect the assembly, it lets us get to th...
It's unlikely, unless it's picking up on a pdb for an assembly which is shared between sites. Please could you save your results and email them to support @ red-gate .com with F0041528 in the subject line along with screenshots of where you think the problem appears? / comments
It's unlikely, unless it's picking up on a pdb for an assembly which is shared between sites. Please could you save your results and email them to support @ red-gate .com with F0041528 in the subje...
While this is in consideration for a future version. I wouldn't expect it any time in version 6. Sorry. / comments
While this is in consideration for a future version. I wouldn't expect it any time in version 6. Sorry.
These seem to largely be added when using the error reporting (and using the error reporting with the sdk). Have you noticed any occurences when not using this feature? I'll be looking into this further to see if any more information can be gathered. / comments
These seem to largely be added when using the error reporting (and using the error reporting with the sdk). Have you noticed any occurences when not using this feature? I'll be looking into this fu...
In general you shouldn't be seeing {smartassembly}.MemoryManagement, SmartAssembly.HouseOfCards, I'm not totally sure why you're seeing these.
You will need SmartExceptionsCore as this is the code that actually compiles and sends in the error report. If SA is adding things to your project, it's likely that they're necessary. / comments
In general you shouldn't be seeing {smartassembly}.MemoryManagement, SmartAssembly.HouseOfCards, I'm not totally sure why you're seeing these.
You will need SmartExceptionsCore as this is the code ...
Please can you check in \windows\fonts and make sure you have the Verdana font installed? / comments
Please can you check in \windows\fonts and make sure you have the Verdana font installed?
Might be worth trying the attach to .net 4 process option to see if you get any different results.
Failing that gather up the logs (found under the help menu, open log folder option) and email them to support @ red-gate .com with F0041142 in the subject line. / comments
Might be worth trying the attach to .net 4 process option to see if you get any different results.
Failing that gather up the logs (found under the help menu, open log folder option) and email them...