Deployment Report Folder

Hi,

I would like to be able to deploy a report to a particular folder in the report server. It seems when I deploy a report it always shows up in the root even after I have moved it into another folder where I wish it to reside.

Thanks,

DD

You set the deployment path of reports (and datasources in 2005) using the project property pages.

Right click on the project (in solution explorer) - select "properties", then if you expand "configuration properties" in the left hand pane of the dialog and select "general"

You can now see the "target report folder" (and if using 2005 "target data source folder")

you can amend this as follows

if you want the following folder

root/adminReports/server

just put

"adminReports/server" in the "target report folder" textbox

|||Right, but that changes the deployment folder for the whole project. I don't seem to be able to change the reports individually. What would be sweet would be if you add folders to your solution and the deployment process puts the reports in the corresponding folders.|||

You have these options:

1) Create 1 solution per folder group that you require, set them to point at the folders you requires

2) Use configuration manager to create different deployment folders, deploy the reports individually once you've picked your target folder using config mgr

3) Use a tool like Reporting Services scripter to generate a deployment script, then edit this (and the winnt folder structure) accordingly - "find in folders" using vs.net is easy enough [http://www.sqldbatips.com/]

|||

Thanks for the valuable tips. I will check out that Linked Report tool.

I ended up creating a project for every folder.

Thanks,

DD

Deploy .NET Assembly with UDFs to a particular SCHEMA

Is it possible to deploy .NET assemblies and the UDF functions therein from Visual Studio.NET into a particular schema?Unfortunately this is not possible through Visual Studio 2005. You would need to write your own script for doing this.
However, you can execute any SQL script during the post deploy process in your SQL Server project as:

1. Write your script into a file called postdeployscript.sql:

2. Add the file to your project by right clicking your project in Solution Explorer and Add à Existing Item.

Make sure you add this in the root of the project and not in the Test Scripts. When you click deploy, Visual Studio will automatically run this scripts after the deployment of your project.
Same holds for predeployscript.sql if you want to execute a script on the SQL server before deployment.

These scripts can be used to automate something that Visual Studio does not currently support.

Thanks,
-Vineet.

|||

postdeployscript.sql and predeployscript.sql are the things I dreamed about all the time . You should definitely include them into default template of SQL Server Project, because I was searching for this solution for two months until I found this post. I asked similar question on the TechNet and the answer was just "you cannot do it".

Deploy .NET Assembly with UDFs to a particular SCHEMA

Is it possible to deploy .NET assemblies and the UDF functions therein from Visual Studio.NET into a particular schema?Unfortunately this is not possible through Visual Studio 2005. You would need to write your own script for doing this.
However, you can execute any SQL script during the post deploy process in your SQL Server project as:

1. Write your script into a file called postdeployscript.sql:

2. Add the file to your project by right clicking your project in Solution Explorer and Add à Existing Item.

Make sure you add this in the root of the project and not in the Test Scripts. When you click deploy, Visual Studio will automatically run this scripts after the deployment of your project.
Same holds for predeployscript.sql if you want to execute a script on the SQL server before deployment.

These scripts can be used to automate something that Visual Studio does not currently support.

Thanks,
-Vineet.

|||

postdeployscript.sql and predeployscript.sql are the things I dreamed about all the time . You should definitely include them into default template of SQL Server Project, because I was searching for this solution for two months until I found this post. I asked similar question on the TechNet and the answer was just "you cannot do it".