To Whom It Concerns -- FWIW, this bug still exists in VS 2013. Visual Studio does NOT update always update a report on the server after deployment. Ug. What a stinky bug. When I deploy my report from VS the deployment "succeeds" but the report is NOT updated on the server. The only sure-fire workaround that I have found is to deploy a new version of the report each time by giving the new version a new file name. So I have "MyReportV01.rdl" then "MyReportV02.rdl" and etc. This forces a new version onto the server and it works find. But, of course, it stinks too because my report name references must be updated in my clients and it leaves orphans on the server. The orphans are not a big deal and I do not care about them and centralizing the report name in config settings mitigates the reference update headache. Still, VS has a bug here and it should just brute-force deploy and save us this workaround. Oh well. Put it on the TODO list MS, please. Yes, this is just one man's experience and your mileage may vary but this bug does exist here in VS2013+Win7+SsrsReportServer2008 fully-patched as of now If you have a real solution, then please post here because I am happy to be be proven wrong in such a case. -- Mark Kamoski
↧