Hi all,
we do have a service written in .NET3.5 (CLR2) which loads some .NET4 (CRL4) assemblies. This works without problems. But when we want to profile the use of the .NET 4 components in the .NET3.5 service we cann't see them at all. My suspect is that the profiler has decided to profile CLR2 and does not check the CLR4. Is there any trick to tell the profiler only to look for CLR4 instead of CLR2? Or much better to tell the profiler to check both runtimes CL§2 and CLR4?
Thanks
Service mixed CLR2 and CLR4
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
Re: Service mixed CLR2 and CLR4
Hello,
Best regards,
Anton
At the moment, only the first loaded CLR is being profiled.My suspect is that the profiler has decided to profile CLR2 and does not check the CLR4.
It seems we can add a option to choose which CLR instance to profile. In your case you'll need to choose version 4. If you are interested, we'll give you a build for testing.Is there any trick to tell the profiler only to look for CLR4 instead of CLR2?
Best regards,
Anton
-
- Posts: 3
- Joined: Mon Feb 11, 2013 8:09 am
Re: Service mixed CLR2 and CLR4
Hi,
yes, that would be great. We need this urgently.
Are there any plans to develop something within the profiler so it can profile any type of runtime in parallel, that would enhance the profiler dramatically.
Thanks
yes, that would be great. We need this urgently.
Are there any plans to develop something within the profiler so it can profile any type of runtime in parallel, that would enhance the profiler dramatically.
Thanks
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
Re: Service mixed CLR2 and CLR4
We'll try to provide it today or tomorrow.yes, that would be great. We need this urgently.
It's technically possible, but would require serious changes in the profiler agent. We'll consider this as a new feature for the next version.Are there any plans to develop something within the profiler so it can profile any type of runtime in parallel, that would enhance the profiler dramatically.
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
Re: Service mixed CLR2 and CLR4
Could you please try to specify startup option "recursive" with the latest released version of the profiler (8.0.3):
http://www.yourkit.com/dotnet/download/
How to specify a startup option:
http://www.yourkit.com/docs/dotnet/help ... ptions.jsp
Since you run a service, you'll likely need to set a system (not user!) variable YNP_STARTUP_OPTIONS and then restart the machine.
If this does not help, please try a build with the new startup option "targetclr=v4":
http://www.yourkit.com/download/tmp/201 ... ld9000.exe
If this doesn't work, please try startup options "targetclr=v4,recursive".
http://www.yourkit.com/dotnet/download/
How to specify a startup option:
http://www.yourkit.com/docs/dotnet/help ... ptions.jsp
Since you run a service, you'll likely need to set a system (not user!) variable YNP_STARTUP_OPTIONS and then restart the machine.
If this does not help, please try a build with the new startup option "targetclr=v4":
http://www.yourkit.com/download/tmp/201 ... ld9000.exe
If this doesn't work, please try startup options "targetclr=v4,recursive".
-
- Posts: 3
- Joined: Mon Feb 11, 2013 8:09 am
Re: Service mixed CLR2 and CLR4
Hi Anton,
the first two options do not work. I have installed V8.0.3 of the profiler, no success. I tried to give the startup options as mentioned "targetclr=v4,recursive", but I get the message
Invalid Option: "targetclr=v4
Having installed 9.0.0 preview does the job. First I thought it is still not working, but after it loads the first .NET 4 assembly the service shows up in the list of .NET applications and our .NET 4 assemblies can be profiled. That is great. But much better would be the ability to transparently profile all clr versions.
Many thanks for your quick response and help.
Regards
Christian
the first two options do not work. I have installed V8.0.3 of the profiler, no success. I tried to give the startup options as mentioned "targetclr=v4,recursive", but I get the message
Invalid Option: "targetclr=v4
Having installed 9.0.0 preview does the job. First I thought it is still not working, but after it loads the first .NET 4 assembly the service shows up in the list of .NET applications and our .NET 4 assemblies can be profiled. That is great. But much better would be the ability to transparently profile all clr versions.
Many thanks for your quick response and help.
Regards
Christian
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
Re: Service mixed CLR2 and CLR4
Hello Christian
Thanks for the feedback.
Did you try 8.0.3 with "recursive" alone?
If possible, could you test all the variants with 9.0.0:
targetclr=v4,recursive
targetclr=v4
recursive
Best regards,
Anton
Thanks for the feedback.
It's OK with version 8.0.3 because this option has just been added in the 9.0.0 internal build.Invalid Option: "targetclr=v4
Did you try 8.0.3 with "recursive" alone?
Could you please clarify: did you use the combination "targetclr=v4,recursive" or only "targetclr=v4"?Having installed 9.0.0 preview does the job.
If possible, could you test all the variants with 9.0.0:
targetclr=v4,recursive
targetclr=v4
recursive
As I wrote, we'll consider this as a new feature.But much better would be the ability to transparently profile all clr versions.
Best regards,
Anton