yes, deploy. When I choose the deploy option, it physically saves it to some My Documents folder - this is the deploy output:
------ Deploy started: Project: Report4, Configuration: Debug ------
Deploying to
Deploying data source '/Data Sources/DataSource1'.
Deploying report '/Report4/Catalog4'.
Deploy complete -- 0 errors, 0 warnings
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
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.