Hi,
I was just trying to test my new custom assemblies on 2005 CTP July
version (I think). The usual directories are not there. I looked up
the documentation and the directories the documentation told me to put
the custom assemblies in are also not there...
Does anyone know where I should put the dll for custom assemblies for
2005 July CTP?
Thanks
Peter
www.peternolan.comI highly recommend downloading the September CTP. Especially if you are
using Reporting Services.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Peter Nolan" <peter@.peternolan.com> wrote in message
news:1127598946.821023.209470@.f14g2000cwb.googlegroups.com...
> Hi,
> I was just trying to test my new custom assemblies on 2005 CTP July
> version (I think). The usual directories are not there. I looked up
> the documentation and the directories the documentation told me to put
> the custom assemblies in are also not there...
> Does anyone know where I should put the dll for custom assemblies for
> 2005 July CTP?
> Thanks
> Peter
> www.peternolan.com
>|||Regarding custom assemblies on RS 2005 - please check the updated online
documentation for RS 2005: http://msdn2.microsoft.com/en-us/library/ms225486
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:O4KuhwWwFHA.900@.TK2MSFTNGP11.phx.gbl...
>I highly recommend downloading the September CTP. Especially if you are
>using Reporting Services.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Peter Nolan" <peter@.peternolan.com> wrote in message
> news:1127598946.821023.209470@.f14g2000cwb.googlegroups.com...
>> Hi,
>> I was just trying to test my new custom assemblies on 2005 CTP July
>> version (I think). The usual directories are not there. I looked up
>> the documentation and the directories the documentation told me to put
>> the custom assemblies in are also not there...
>> Does anyone know where I should put the dll for custom assemblies for
>> 2005 July CTP?
>> Thanks
>> Peter
>> www.peternolan.com
>|||Hi Bruce,
thanks...I got a note from dundas on their new beta and it being
recommended on the september CTP.....but I am travelling again so I
will fetch all the 'new stuff' next time I on my own dime...
Thanks
Peter|||Hi Robert,
I followed the documentation you pointed to and copied my custom
assembly as put new code groups into the config files as specified..I
still get the message 'The application for BI4ALL.rptproj is not
installed' when I try to open up my visual studio project.....I have
an old version and the only difference is the custom assembly (I
believe).
Do you (or anyone else) have any ideas what else I might have to do?
Thanks
Peter
To deploy a custom assembly in Reporting Services
Copy your custom assembly from your build location to the report server
bin folder or the Report Designer folder. The default location of the
bin folder for the report server is C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportServer\bin. The default
location of the Report Designer is C:\Program Files\Microsoft Visual
Studio 8\Common7\IDE\PrivateAssemblies.
If you need to grant your custom assembly code permissions beyond the
default execute permissions:
Open the appropriate configuration file. The default location of
rssrvpolicy.config is C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer. The default location of
rspreviewpolicy.config is C:\Program Files\Microsoft Visual Studio
8\Common7\IDE\PrivateAssemblies.
Add a code group for your custom assembly. For more information, see
Understanding Code Access Security in Reporting Services.
<CodeGroup class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Name="MyCodeGroup"
Description="Code group for my data processing extension">
<IMembershipCondition class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\bin\Microsoft.Samples.ReportingServices.FsiDataExtension.dll"
/>
</CodeGroup>|||What do you mean with you "have an old version"? RS 2005 report projects
require the installation of BI Development Studio to open successfully. Can
you create report projects without custom assemblies in BI Development
Studio successfully?
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Peter Nolan" <peter@.peternolan.com> wrote in message
news:1127651973.385470.44280@.g49g2000cwa.googlegroups.com...
> Hi Robert,
> I followed the documentation you pointed to and copied my custom
> assembly as put new code groups into the config files as specified..I
> still get the message 'The application for BI4ALL.rptproj is not
> installed' when I try to open up my visual studio project.....I have
> an old version and the only difference is the custom assembly (I
> believe).
> Do you (or anyone else) have any ideas what else I might have to do?
> Thanks
> Peter
> To deploy a custom assembly in Reporting Services
> Copy your custom assembly from your build location to the report server
> bin folder or the Report Designer folder. The default location of the
> bin folder for the report server is C:\Program Files\Microsoft SQL
> Server\MSSQL.3\Reporting Services\ReportServer\bin. The default
> location of the Report Designer is C:\Program Files\Microsoft Visual
> Studio 8\Common7\IDE\PrivateAssemblies.
> If you need to grant your custom assembly code permissions beyond the
> default execute permissions:
> Open the appropriate configuration file. The default location of
> rssrvpolicy.config is C:\Program Files\Microsoft SQL
> Server\MSSQL\Reporting Services\ReportServer. The default location of
> rspreviewpolicy.config is C:\Program Files\Microsoft Visual Studio
> 8\Common7\IDE\PrivateAssemblies.
> Add a code group for your custom assembly. For more information, see
> Understanding Code Access Security in Reporting Services.
>
> <CodeGroup class="UnionCodeGroup"
> version="1"
> PermissionSetName="FullTrust"
> Name="MyCodeGroup"
> Description="Code group for my data processing extension">
> <IMembershipCondition class="UrlMembershipCondition"
> version="1"
> Url="C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\bin\Microsoft.Samples.ReportingServices.FsiDataExtension.dll"
> />
> </CodeGroup>
>|||Hi Robert,
yes, projects without custom assemblies are fine..
What I meant was I have a version of our reports with no custom
assemblies and they upgrade and can be previewed in BI Dev studio just
fine...they can also be deployed to reporting services web server just
fine....
When I try to copy the version of our reports with the Custom Assembly
across to 2005 I get the message 'The application for BI4ALL.rptproj is
not installed' when I try to open up my visual studio project.....So,
I am guessing it is still the CA...
I have gone through all the steps in the documentation referenced but
still cannot get the project to open...
So, I am looking for hints as to whether it is the CA and if so how I
might get it it work..
Thanks
Peter|||Hi All,
I am still working on this...Has anyone else got custom assemblies
working on July CTP for SQL Server?
Thanks
Peter|||Hi All,
thought I would add my latest efforts to trying to get my reports to
migrate across. I have got my custom assembly working on 2005...I was
able to add the custom assembly to the old version of my project and
have it run and work...so I no longer think my error message is related
to the customer assembly.
I searched this group for the message 'The application for project
'xxx.rptproj' is not installed. Make sure the application for the
project type (.rptproj) is installed.
I found this entry on the group about clearing public and private cache
but how do I clear these caches?
http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/7e68c4de6af07a72/7bed68d9e4214e23?q=make+sure+application+for+project+type+is+installed&rnum=1&hl=en#7bed68d9e4214e23
All ideas most welcome!!!
How did I get custom assemblies to work you may ask...
Well on CTP July.
I cannot find:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer
I can only find...
D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer
where the following config files reside...
rsreportserver.config
rssrvpolicy.config
web.config
http://msdn2.microsoft.com/en-us/library/ms225486
says the following...
To deploy a custom assembly in Reporting Services
Copy your custom assembly from your build location to the report server
bin folder or the Report Designer folder. The default location of the
bin folder for the report server is C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportServer\bin. The default
location of the Report Designer is C:\Program Files\Microsoft Visual
Studio 8\Common7\IDE\PrivateAssemblies.
If you need to grant your custom assembly code permissions beyond the
default execute permissions:
Open the appropriate configuration file. The default location of
rssrvpolicy.config is C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer. The default location of
rspreviewpolicy.config is C:\Program Files\Microsoft Visual Studio
8\Common7\IDE\PrivateAssemblies.
Add a code group for your custom assembly. For more information, see
Understanding Code Access Security in Reporting Services.
So I added these entries to my config files...
Snipped from my rssrvpolivy.config file..
<CodeGroup class="FirstMatchCodeGroup" version="1"
PermissionSetName="Nothing">
<IMembershipCondition class="AllMembershipCondition"
version="1" />
<CodeGroup class="UnionCodeGroup" version="1"
PermissionSetName="FullTrust" Name="IBIRSCustomClass"
Description="IBIRSCustomClass">
<IMembershipCondition class="UrlMembershipCondition"
version="1" Url="D:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting
Services\ReportServer\bin\IBIRSCustomClass.dll"/>
</CodeGroup>
<CodeGroup class="UnionCodeGroup" version="1"
PermissionSetName="Execution"
Name="Report_Expressions_Default_Permissions" Description="This code
group grants default permissions for code in report expressions and
Code element. ">
<IMembershipCondition
class="StrongNameMembershipCondition" version="1"
PublicKeyBlob="0024000004800000940000000602000000240000525341310004000001000100512C8E872E28569E733BCB123794DAB55111A0570B3B3D4DE3794153DEA5EFB7C3FEA9F2D8236CFF320C4FD0EAD5F677880BF6C181F296C751C5F6E65B04D3834C02F792FEE0FE452915D44AFE74A0C27E0D8E4B8D04EC52A8E281E01FF47E7D694E6C7275A09AFCBFD8CC82705A06B20FD6EF61EBBA6873E29C8C0F2CAEDDA2"
/>
</CodeGroup>
Snipped from my rspreviewpolicy.config file...
<CodeGroup class="FirstMatchCodeGroup" version="1"
PermissionSetName="Nothing">
<IMembershipCondition class="AllMembershipCondition"
version="1" />
<CodeGroup class="UnionCodeGroup" version="1"
PermissionSetName="FullTrust" Name="IBIRSCustomClass"
Description="IBIRSCustomClass">
<IMembershipCondition class="UrlMembershipCondition"
version="1" Url="D:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting
Services\ReportServer\bin\IBIRSCustomClass.dll"/>
</CodeGroup>
<CodeGroup class="UnionCodeGroup" version="1"
PermissionSetName="Execution"
Name="Report_Expressions_Default_Permissions" Description="This code
group grants default permissions for code in report expressions and
Code element. ">
<IMembershipCondition
class="StrongNameMembershipCondition" version="1"
PublicKeyBlob="0024000004800000940000000602000000240000525341310004000001000100512C8E872E28569E733BCB123794DAB55111A0570B3B3D4DE3794153DEA5EFB7C3FEA9F2D8236CFF320C4FD0EAD5F677880BF6C181F296C751C5F6E65B04D3834C02F792FEE0FE452915D44AFE74A0C27E0D8E4B8D04EC52A8E281E01FF47E7D694E6C7275A09AFCBFD8CC82705A06B20FD6EF61EBBA6873E29C8C0F2CAEDDA2"
/>
</CodeGroup>
And then it all seems to work ok.... :-)
Hope this helps someone else :-)
Peter
www.peternolan.com