Thanks for the response. We tried that. It seems that no matter what, VS
always wants to deploy these things. We are running using DebugLocal which
uses the RSReportHost as report container. So, we always click the
run/execute button or hit f5.
I guess we will see what the support folks say.
"Bruce L-C [MVP]" wrote:
> What you could do is just remove the configuration info totally. If there is
> not a server specified to deploy to it won't be able to deploy.
>
> The main time I deploy by mistake is when I hit on what would be the execute
> button. I am going back and forth between vb.net and designing reports and
> by mistake I sometimes hit it and then it merrily tries to deploy
> everything. Arghh.
>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Paul J. Boyes" <PaulJBoyes@discussions.microsoft.com> wrote in message
> news:F1D32F05-7157-484F-A0DA-8F8CEB3B4C1E@microsoft.com...
> > Hello,
> >
> > My team has been having a very annoying problem where Visual Studio always
> > deploys the reports in a project even when you turn Deploy off in the
> > Configuration Manager. The ideal solution for us is to be able to run the
> > the reports locally using RSReportHost (not a local report server) and
> > DebugLocal as we are using custom assemblies and doing debugging
> > regularly.
> >
> > This happens on several development machines. I have support call open,
> > but
> > they cannot seem to get to the bottom of this. Any ideas as to what may
> > be
> > going on? Any input you have would be greatly appreciated.
> >
> > Thanks,
> >
> > Paul J. Boyes
> > Lead Developer
> > Madigan Army Medical Center
>
>
