December 2, 2009 at 1:33 am
I have a report project that relies on a custom assembly. I just today made the switch to Windows 7 and the directory that I used to put my custom assembly in no longer exists! In Windows XP I put the assembly in:
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies
Now, when I go to the IDE folder in that path, there is no directory named PrivateAssemblies. Any ideas on where custom assemblies go in Windows 7 development environments?
December 8, 2009 at 11:27 am
tnk (12/2/2009)
I have a report project that relies on a custom assembly. I just today made the switch to Windows 7 and the directory that I used to put my custom assembly in no longer exists! In Windows XP I put the assembly in:C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies
Now, when I go to the IDE folder in that path, there is no directory named PrivateAssemblies. Any ideas on where custom assemblies go in Windows 7 development environments?
I am running Windows 7 Ultimate and I found the PrivateAssemblies sub folder in the IDE folder in a few seconds so you need to look again.
Kind regards,
Gift Peddie
December 9, 2009 at 4:31 am
I figured it out. I am running the 64-bit version of Windows 7 and I was rushing and failed to make the distinction between "Program Files" and "Program Files (x86)". The path in question is in the latter directory. Thanks for the response.
December 12, 2009 at 8:16 am
Hi,
Please check the following links.
Custom Assembly in Reporting Services:
December 12, 2009 at 8:39 am
becklery (12/12/2009)Hi,
Please check the following links.
Custom Assembly in Reporting Services:
http://msdn.microsoft.com/en-us/library/ms155034.aspx%5B/quote%5D
You need to install Windows 7 before you can answer this thread what you are saying is not related to the issue. This is physical file location in your hard drive stop answering questions I have answered.
Kind regards,
Gift Peddie
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply