If you really mean it is trying to deploy to MyDocs then deployment path can be changed by right clicking on solution in solution explorer and choosing "properties" then changing it in there
If you mean the default save location, that is set up as part of the project initiation - not sure what the best way to move it would be - in the past I've simply copied the whole folder from one area and pasted it where I want it then open from there instead...
Rgds, Geoff
We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.
The report is then physically created in My Documents/Visual Studio/Projects/Report4/Catalog4. Since I didn't set up SRSS originally, it seems to me the guy who installed it took some default.
When I pull the report via the web in my vb.net app, I am using the Web Services ReportExecutionServices class, which takes '/Report4/Catalog4' as a parameter to rs.LoadReport(reportpath,etc) where reportpath = /Report4/Catalog4. Everything works ok, but I have a catalog of 60 reports to convert from Access to SRSS so before I get into this to deep I want to set up the deployment path correctly.
We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.
when you right click on the report project in the solution explorer and choose "Properties", you should get a box pop up with a whole bunch of properties.
TargetServerURL
which should be on the lines of:
TargetReportFolder
which represents the folder path from the root above
You say you only get a single folder name? I wonder if you are using an Integration Services or ASP.NET type project rather than an SSRS type project...?
If that is the case, you may have to manually migrate your reports to the reportserver but that is something I've never had to do I am afraid...
Rgds, Geoff
We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.
Yes, I get all that, but the problem is the physical location of the deployed files on the file server. I deploy to /servername/Reportserver, and the physical location of the deployed files that the report server is reading from is some \admin\My documents folder. I'm not having any problems retrieving the reports in any application, I am just looking for where the reportserver maps the physical location of the deployed files so I can change it to a different physical disk folder so that some network guy doesn't come along and delete all my reports from his admin folder.
As far as I am aware, the reportserver reads from the reportserver database not a physical location...
You have physical files which belong to your VS / BIDS project which are typically stored in a mydocs area but when deployed they should go into the reportserver database which is what the reportserver reads from..
Rgds, Geoff
We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.
That actually makes perfect sense, then I wonder, why the .rdl files on the disk? They appear everytime I hit "deploy". Perhaps the "Build" function in Visual Studio is creating them? I think I'll back them up somewhere, delete them and see what happens.....
RDLs are the report files themselves - that is what you would upload to the report server if you were deploying via web browser. Build builds the RDLs and then deploy sticks them into the report server you specify using "web services."
Yes, I understand how the web services work, and I have already deployed an app using them, but this is what I am seeing: I create the report, it asks me for a disk file location, I type in "C:\MfgReports\ReportSomeReport" and it creates the reports and dataset stuff in that physical directory. At some point, I choose Build, then Deploy, and the results window shows me the Fail/Succeed messages, and from this I cut and paste the virtual folder it returns, which is http:\\SomeSqlBox\ReportServer\MfgReports\ReportSomeReport" into my web app, everything works fine. But for some reason, it also creates only the rdl's in the Administrator's My Document\Visual Studio\Projects folder. At this point, I think I am going to conclude that deleting these will not break the app, however I will test it out first. I think VS is creating them.
When you build your report project there is an output in the form of files. Those files go into a folder. You specify that folder - by default it is within a visual studio hierarchy in the users documents directory. I imagine you are doing your report writing as Administrator so your default directory for projects is inside the Administrator's document directory. The deploy step takes those files and sticks them in report server. Instead of deleting those files you should be putting them in source control.
regards
1: your "source" set which are typically saved within the solution directory created in VS - by default I think this is set to MyDocs\Visual Studio (version)\SolutionName\SolutionName\
with the .rdl, .ds and .user files all in the lowest level of that path
2: your "deployed" set which are the ones the reports physically run off which are stored in the reportserver database. If you delete your local "hard copies" of the files they can be retrieved from the reportserver buy going into the report and choosing "edit" - this will allow you to save the rdl file that is stored in the reportserver database to wherever you want
Rgds, Geoff
We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.