Reflecting classes with names forbidden on Win filesystem

[ksafonov]

Hello all,

I'm trying to use Reflector Visual Studio plugin (v.6.1.0.11) to debug TFS client API.

When I try to add Microsoft.TeamFoundation.dll assembly as a debugged one, I get the following error while 'Saving decompiled assembly to debug store':

System.ArgumentException: FileStream will not open Win32 devices such as disk partitions and tape drives. Avoid use of "\\.\" in the path. ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 6324, offset:851 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 6322, offset:223

The reason I see is that the assembly contains class named
'Microsoft.TeamFoundation.Server.Aux', and Reflector tries to create file named 'Aux.cs' or similar during decompilation. Surely, Windows won't allow that: http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx?PHPSESSID=c0b8b2e8ed0e1bb5852e06dadac5d1a9#naming_conventions

Is there any way to workaround this?
This really stops my further work

Thanks in advance,
Kirill

[Clive Tong]

Hi.

Thanks for reporting that. I don't know of any workaround, but on Monday I'll have a look at putting a fix into the next EAP of Reflector 6.5.

Clive

[ksafonov]

Hi Clive,

Thanks for quick response,

Looking very much to that since it's really a blocker for me.

Many thanks,
Kirill

[Clive Tong]

I put a fix into the Reflector 6.5.0.123 EAP which you can download from the EAP forum.

http://www.red-gate.com/messageboard/viewforum.php?f=117

[ksafonov]

Hello Clive,

Thanks a lot for such a quick fix,

I can confirm it works for me now. Will report if something arises.

The best wishes to continue developing such a great product!

Many regards,
Kirill

[fabiocoutinho]

[Clive Tong]

The link used to point to the EAP (early access version) of Reflector 6.5. That version has now been released - you can get it by using Help/Check For Updates on your existing version of Reflector, or by downloading the latest version from the Red Gate site.

[fabiocoutinho]

Hello Clive,

After updating the reflector, to export the dll the following error appears:


Microsoft\TeamFoundation\Server\Aux.cs
System.NullReferenceException: Object reference not set to an instance of an object.
at .
‡ƒ.“(Exception , Int32 , Object[] )
at ‘.�.WriteTypeDeclaration(ITypeDeclaration , String , ILanguageWriterConfiguration )
at ‘.�.()
1 error(s).
Done.

You can give some direction so I can proceed?

Tkank's

[Clive Tong]

The fix I made was to handle the special path components when an assembly is decompiled using Reflector Pro. I didn't make an equivalent fix on the code path that deals with the "Export" functionality in Reflector.

Currently, the best workaround is probably to decompile the assembly using Reflector Pro and then generate a project file yourself.