Comments
Sort by recent activity
Glad to hear that! [image] / comments
Glad to hear that!
Sorry to hear you're experiencing some trouble! Can I first make sure--are you using the Standard or Professional version of the profiler? Database calls are only available with the Pro version, I'm afraid.
If you are already using the Pro version, you may want to try running the profiler explicitly as administrator in case there are any permissions issues. Please let me know if that helps! / comments
Sorry to hear you're experiencing some trouble! Can I first make sure--are you using the Standard or Professional version of the profiler? Database calls are only available with the Pro version, I'...
Hi Wout,
I found some older tickets regarding this error and it's true that using a lower level of obfuscation should help. Thank you for posting this! [image] / comments
Hi Wout,
I found some older tickets regarding this error and it's true that using a lower level of obfuscation should help. Thank you for posting this!
Hi Nicola!
Automatically profiling IIS express from VS2010 still does not work I'm afraid, however, I'm very happy to report that you should soon be able to do this with VS2012! I will let you know once the v.8 beta build with the bug fix goes out. [image] / comments
Hi Nicola!
Automatically profiling IIS express from VS2010 still does not work I'm afraid, however, I'm very happy to report that you should soon be able to do this with VS2012! I will let you know...
I don't quite know if it will be fixed for version 8 as there has not been a timeline set, but I will definitely keep an eye on this issue and keep you posted!
And again, so sorry that this isn't working--I realize it's a bit annoying, but I hope using the standalone profiler won't be too much of a pain! / comments
I don't quite know if it will be fixed for version 8 as there has not been a timeline set, but I will definitely keep an eye on this issue and keep you posted!
And again, so sorry that this isn't w...
So sorry about the delay in getting back to you! I'm afraid there's no time frame set at the moment, but can I make sure--are you still able to profile by launching your application from the standalone profiler?
Please also let me know if you are in need of a trial extension! / comments
So sorry about the delay in getting back to you! I'm afraid there's no time frame set at the moment, but can I make sure--are you still able to profile by launching your application from the standa...
Thanks very much for your post. I'm afraid you're right--this is a bug with the VS 2012 add-in and IIS Express wherein choosing to "profile performance" of an IIS Express app from the add-in will not automatically start profiling the application as it should. We've logged this issue in our system with reference PP-1796--so sorry for the inconvenience it causes at the moment! / comments
Thanks very much for your post. I'm afraid you're right--this is a bug with the VS 2012 add-in and IIS Express wherein choosing to "profile performance" of an IIS Express app from the add-in will n...
Hi Hugh,
I'm working with you again through email, but I didn't want your forum post to feel neglected [image]
As I've mentioned, the issue with how SmartAssembly handles versioned dependencies is a known bug (SA-31). This bug exists because SmartAssembly unfortunately has no way of knowing what paths were used by the original VS project (as they're not stored in the resulting assembly) and as a result, SA might end up using a different assembly that has a similar name even if it has a different version or is from a different location than the original (in some way though, this is actually a good thing as it would help when users are retargeting assemblies against later .Net versions). Again, I'm very sorry about this and the risk of runtime issues it might cause but at the moment, the only workaround is the MandatoryPath attribute.
However, I have just recalled a bit of a hacky workaround--if SmartAssembly cannot find youre dependencies when it first loads your project, it will prompt you to browse and point to the needed DLL. If you can hide your dependencies (i.e. move them outside of the main assembly's folder), you can then point SmartAssembly to the right DLLs.
Regarding the ability to specify MandatoryPaths from the UI, I'd also created a feature request (with SA-1591), although I do not know any timeline for this at the moment. / comments
Hi Hugh,
I'm working with you again through email, but I didn't want your forum post to feel neglected
As I've mentioned, the issue with how SmartAssembly handles versioned dependencies is a known...
Hi there,
Just to be sure, have you got "Profile child processes" enabled in the Application Settings? / comments
Hi there,
Just to be sure, have you got "Profile child processes" enabled in the Application Settings?
Hi again Hugh [image]
As I mentioned in your ticket, SmartAssembly choosing the wrong dependencies is indeed a bug. It is unfortunate, but as I understand it, this behavior is kept as it's important for applications running on different frameworks.
When this behavior causes issues, the workaround is to use the MandatoryPath. However, you're right that it would be a good idea to warn users that a different dependency was used, regardless of whether or not it causes any obvious errors. I've created a feature request for this (with reference SA-1593). Thank you for the suggestion and again, sorry that you're experiencing this issue [image] / comments
Hi again Hugh
As I mentioned in your ticket, SmartAssembly choosing the wrong dependencies is indeed a bug. It is unfortunate, but as I understand it, this behavior is kept as it's important for ...