4.6.1 migrating to .Net Core 7 – How do I resolve error MC1000- cannot find type System.Management.Instrumentation.InstrumentedAttribute in Assembly ..path \.nuget\packages\system.management\7.0.0\lib\net6.0\SystemManagement.dll – Microsoft.WinFx.Targets

Dozier, Fletcher [US] (DS) 1

I am migrating a .netFramework 4.6.1 application to core. I have been able to get rid of all of the build errors except this one:

Error MC1000 Unknown build error, 'Could not find type 'System.Management.Instrumentation.InstrumentedAttribute' in assembly 'C:\Users\xxxxx.nuget\packages\system.management\7.0.0\lib\net6.0\System.Management.dll'.'
AppName C:\Program Files\dotnet\sdk\6.0.402\Sdks\Microsoft.NET.Sdk.WindowsDesktop\targets\Microsoft.WinFX.targets 223

This has been a blocker for about a month now. Does anyone have any idea regarding how the error can be solved? I have adde references to system.management, system.management.Instrumentation.... etc. But it seems like instrumentedAttribute is no longer part of the namespace.

Best Regards.

Tianyu Sun-MSFT 27,266 Reputation points Microsoft Vendor

2022-11-29T08:38:42.027+00:00

Hi @Dozier, Fletcher [US] (DS) ,

Welcome to Microsoft Q&A forum. I have checked the System.Management.Instrumentation assembly and System.Management package. Looks like the InstrumentedAttribute is not included in any of them just like you said. Are you using InstrumentedAttribute/System.Management in your project/solution? Or is there any referenced package dependents on it?
Dozier, Fletcher [US] (DS) 1 Reputation point

2022-11-29T15:54:40.393+00:00

Good morning!
Thanks for your response. This is an inherited desktop app that we are converting to core. I cannot find instrumentedAttribute being used directly in any class. I see a hintpath for system.management in one of the projects. The error is being thrown in relation to the base project it seems. Documentation found online states that it should be part of the system.management.instrumentation namespace. https://learn.microsoft.com/en-us/dotnet/api/system.management.instrumentation.instrumentedattribute?view=netframework-4.8

In the object browser, I see two references to 'system.management.instrumentation'. One is listed as member of 'system.management.Instrumentation'. The other is listed as member of 'System.Core'. When I look at the 'pre-migrated' version of the App, I see only the 'system.management.Instrumentation' in 'system.core' listed in the object browser. I don't see anywhere that the 'instrumentedAttribute' is actually used. System.management appears to have been added during the migration to .netCore 6??

Looking at the original version, it doesn't seem to be using it, unless 'Telerik' is using it somehow. I'm not sure how to check if there is a 'referenced package' depending on it?

The error is referring to the 'MarkupCompilePass1' section of the Microsoft.WinFX.Targets file.

v/r
Tianyu Sun-MSFT 27,266 Reputation points Microsoft Vendor

2022-11-30T07:43:55.783+00:00

Hi @Dozier, Fletcher [US] (DS) ,

Thanks for sharing more details. I notice that the path in the error message points to .nuget(nuget packages) folder, it seems that when the error first appeared, the System.Management NuGet package had been installed. And you said there’s a related hintpath in one of the projects, can you confirm that this nuget package was installed by yourself or it was downloaded and installed automatically during the process of migrating? Does restoring nuget packages fix this issue? And are you using any extensions?

1 answer

Hardik Patel 0 Reputation points

2023-02-03T21:47:03.9733333+00:00

Hi @Dozier, Fletcher [US] (DS) ,

Did you get fix for this problem?

I am trying to convert windows service from .net framework to .net core but one of referenced dll is using InstrumentedAttribute/System.Management. I am not able to get ahead from this. I tried to use System.Management and windows.compatability package from .nuget.

Please advise.

Thanks!
Please sign in to rate this answer.
Dozier, Fletcher [US] (DS) 1 Reputation point

2023-02-07T14:49:25.6+00:00

Hello @hardik patel

Sorry to say, but I was not able to get pass this one last error during my effort. This is a blocker for me. Of course Microsoft doesn't seem to care when they force changes upon their customers. At the moment, I'm dead in the water with this one!
Sign in to comment