I'm trying to open an old 1.1 assembly in JustDecompile and it's giving me an error. "JustDecompile supports only valid CLR assemblies.".
I assume this is because I'm on a Windows 8 machine? If so is there any way around this issue? We have a very old (8 years) assembly and we're trying to confirm if there are any differences between the old code we have in source control compared to what's actually running on our servers.
I assume this is because I'm on a Windows 8 machine? If so is there any way around this issue? We have a very old (8 years) assembly and we're trying to confirm if there are any differences between the old code we have in source control compared to what's actually running on our servers.
6 Answers, 1 is accepted
0
Hi PJ,
I'm sorry for the inconvenience. It seems like JustDecompile can't recognize the assembly as a .NET assembly. Is it possible that it's not a .NET assembly? Can you please share the assembly in order to investigate?
Kind regards,
Vladi
Telerik
I'm sorry for the inconvenience. It seems like JustDecompile can't recognize the assembly as a .NET assembly. Is it possible that it's not a .NET assembly? Can you please share the assembly in order to investigate?
Kind regards,
Vladi
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
PJ Melies
Top achievements
Rank 1
Rank 1
answered on 10 Jun 2014, 05:21 PM
It's definitely a .Net 1.1 assembly. I'm able to open it in Reflector without any issue.
I've opened a ticket with the .dll attached - ticket ID 828137.
I've opened a ticket with the .dll attached - ticket ID 828137.
0
Hello PJ,
I'll answer you in the ticket but will paste the resolution here as well as and if we find it. In order to share it with the rest of the community.
Thanks,
Vladi
Telerik
I'll answer you in the ticket but will paste the resolution here as well as and if we find it. In order to share it with the rest of the community.
Thanks,
Vladi
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
binki
Top achievements
Rank 1
Rank 1
answered on 13 Jan 2015, 05:41 PM
[quote]Vladi said:I'll answer you in the ticket but will paste the resolution here as well as and if we find it. In order to share it with the rest of the community.[/quote]
What did the solution turn out to be?
What did the solution turn out to be?
0
PJ Melies
Top achievements
Rank 1
Rank 1
answered on 13 Jan 2015, 11:58 PM
There was no solution. Telerik was unable to replicate the error I was seeing. They suggested a few things - none of which worked. I ended up using Reflector on this particular assembly.
This was the only assembly I've had trouble decompiling with JustDecompile. Everything else I've worked worth was handled without issue.
This was the only assembly I've had trouble decompiling with JustDecompile. Everything else I've worked worth was handled without issue.
0
Hi,
There is a chance JustDecompile will do that when there is a .pdb file with the same file name as the assembly residing at the same path and there is a problem with reading that .pdb file. That behavior is fixed in the upcoming release. A workaround in the current release would be moving the .pdb file to a different location.
Regards,
Tsviatko Yovtchev
Telerik
There is a chance JustDecompile will do that when there is a .pdb file with the same file name as the assembly residing at the same path and there is a problem with reading that .pdb file. That behavior is fixed in the upcoming release. A workaround in the current release would be moving the .pdb file to a different location.
Regards,
Tsviatko Yovtchev
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.