>>How can I move/copy/export a project in Visual Studio 2005
You don't. I recommend re-deploying the rdl's to the new server for a clean setup.
You're question is a bit confusing also. You don't move a project. The project is simply how you develop your reports in VS. When you deploy the reports/data sources etc.. they go to SSRS and that is it. Can you explian what you mean? Are you trying to open the projects directly on the server? If so that is also not recommended. VS takes far too much resources for you to develop the actually reports on it. I may have missed a deployment method somewhere to so I may be off
[sub]____________ signature below ______________
I am Tedward Keyboardhands!!!
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]
As you can tell, I'm just getting started with SQL Reporting Services.
What I hope to do is develop a report in my office using VS2005. Then, move the report to my clients VS2005 system,
make a few more changes to the report, and deploy the report
on their SSRS.
As a test, I copied the folder containing the report (under the projects folder) to another workstation with VS, but I received the ".rptproj is not installed" error, when I open it.
Does that other machine have the abililty to edit database projects?
Really the process doesn't seem that hard. If I were you and what I've done in the past to make reports "mobile" is use RSScripter to grab the rdl file only.
Basically developer your reports. Deploy them to your test server and instance (this can be local).
Run RSScripter on that instance and it will export from the SSRS instance all the requirements for you to take those reports and move them (in file form). The stripted version would be the .rdl file only. Typically data sources aren't going to be the same along with security so you don't want that anyhow.
Once you ahve the .rdl files you just pop them into a machine that has the ability to edit with BIDS (or database projects in VS.NET). Add them to a new project as Existing Items and rebuild the data sources etc... and you're done. Deploy them as you would normally then to the server
Make sense?
[sub]____________ signature below ______________
I am Tedward Keyboardhands!!!
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]
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.