Best Practices for RS and VSS

We are starting to use VSS2005 for storing projects and rdl files. We are
mainly using it for the versioning capabilities in VSS. Does anyone have any
tips for best practices on how to utilize Visual Studio 2005 and VSS 2005?
IF anyone has a link or two to sites that go over this topic that would be
helpful too.
The problem have had so far is trying to check out the rdl files through VSS
and then open them in Visual Sutdio to edit them. Whenever I have checked
out a file in VSS and then opened the file using the options in VSS to get to
Visual Studio (devenv) I either get a message stating that the carriage
return is messd up in the file or it opens the rdl code... not the designer
window.
If I check out the file in VSS and then open the file through Visual Studio
without using VSS to get to Visual Studio, everything works fine, but that
just seems a little too manual. Thanks in advacne for your help.On Jul 5, 4:50 pm, bsod55 <bso...@.discussions.microsoft.com> wrote:
> We are starting to use VSS2005 for storing projects and rdl files. We are
> mainly using it for the versioning capabilities in VSS. Does anyone have any
> tips for best practices on how to utilize Visual Studio 2005 and VSS 2005?
> IF anyone has a link or two to sites that go over this topic that would be
> helpful too.
> The problem have had so far is trying to check out the rdl files through VSS
> and then open them in Visual Sutdio to edit them. Whenever I have checked
> out a file in VSS and then opened the file using the options in VSS to get to
> Visual Studio (devenv) I either get a message stating that the carriage
> return is messd up in the file or it opens the rdl code... not the designer
> window.
> If I check out the file in VSS and then open the file through Visual Studio
> without using VSS to get to Visual Studio, everything works fine, but that
> just seems a little too manual. Thanks in advacne for your help.
This is a kind-of undocumented territory. This link might be of
assistance.
http://geekswithblogs.net/VROD/archive/2006/11/22/97817.aspx
Also, if VSS 2005 is not suitable, you could try Subversion or some
other Source Control software.
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

Best Practice for Report Projects Related To Application Solutions

Hello Reporting Services Gurus!

I'm about to start on my first reporting services project, but before I mess it up, I'm looking for some guidance on how best to achieve my mission. Here's what I'm looking to achieve:

I have a datacentric application (SQL Server 2005 Express w/ Advanced Services backend) in which I want to build about 50 "canned" reports for the end users. I want to build the reports utilizing server mode so I can take advantage of some of Reporting Services advanced features. I'm not sure what the best practice would be to build the reporting services project. Is it better to include the report project as another project within the application solution? Or, should I build the report project independent of the application solution? What are the pros and cons of doing it either way? How does including the report project build if it's included in the application solution? How would a ClickOnce deployment deploy the report project to the report server?

My ultimate goal would be to have an "off-the-shelf" software solution that includes an installation package consisting of the application project and report project. Is it even possible due to the Reporting Services architecture to achieve an install in this manner with ClickOnce, Windows Installer, or Installshield? Or, is building the report project indepedent of the application project and deploying the reports to the report server "manually" (i.e. deploy within the report server project) the only solution?

Any help would be greatly appreciated!

Tony

I haven't received any feedback yet, so I thought I'd try bumping it back to the top of the thread.

Thanks for any help!

Best Edition & Licensing Option(s)

Hi there:

I'm an independent developer with a few projects for which I'd like to use SQL Server 2000, but I'm not exactly sure which licensing option to choose.

I've got a single-processor machine on which I'll be running the SQL Server instance, and this single instance will support up to a dozen or so separate databases, each of which will be used to power a small public Web site. From what I've read thus far, it appears the Standard Edition single-processor version & license would be most appropriate, but $5,000 is a little more than my budget can handle right now. Is there another viable option available for a situation like this?

Many thanks,
ChrisHave you considered MSDE (SQL Desktop Engine). It is ditributed free with Microsoft Office 2000/XP. There is no licensing.

The only limit is that a dtabase can't grow bigger than 1.5GB hich could be sufficient in your case.

Try these links

Choosing an edition
http://www.microsoft.com/sql/techinfo/planning/SQLResKChooseEd.asp

More about msde:
http://www.microsoft.com/sql/techinfo/development/2000/MSDE2000.asp|||Can MSDE be licensed to run in production? (From what I've read, it appears it can, as long as one possesses a properly licensed version of one of a number of MS products, including VS.NET.)

Any help is sincerely appreciated.

Thanks,
Chris|||Let say you develop an application using MS VS.NET, you can include MSDE as part of your application as the Data Engine.

So in your case it's fine if you are using ASP.Net