I've recently designed a report which uses a new ttf font file to create a barcode image.
I would like to add this as some form of dependency check to SSRS project so that it checks and if necessary installs the font during deployment.
Does anyone know if this functionality is built in to VS somewhere or what best practice is for this scenario?
(Note: SQL2012 SP2 db, VS2010 solution)
Not ideal but since there were no suggestions and I didn't find any automated way I had to add a manual font installation step to deployment documentation for report.
Related
I just created a Report Project with 1 .rdl in Visual Studio 2008. I then deployed the report to the SSRS Server and I can now see the report in the Report manager.
I made a change to the report using report builder 3.0.
Is there a way that I can "get latest version" from the report server of the .rdl when I open my report project in Visual Studio again?
I am guessing that 1 way would be to download the .rdl and add back (overwriting) to the report project but I am wondering if VS has a built in function to take care of this for you?
There is no built in functionality in VS to attach to an SSRS instance and pull down the .rdl files. Since they can be moved, edited and deleted, outside of the designer there could be numerous issues with doing that. Just check all your local project files into source control and manually update if needed. Since I don't edit outside of VS I never had to deal with "pulling the latest version from ssrs". However, I have come across third party tools that may have functionality to make it easier.
If this is going to become a daily struggle for you then you may want to take the time now to automate the process using the ReportExecution2010 or ReportExecution2005 web service api.
Visual Studio is used to create and deploy reports, once they are deployed, there are no links between the report in Visual Studio and the Report Server, and there will never be. Think about it, you can deploy the report to X servers, so how could Visual Studio find which report you are talking about.
To ensure you are working on the latest version, you will have to download it and overwrite as you say, although I would compare it instead to see if there are changes not deployed.
If you are working with other developers that would potentially redeploy the report, then you can just check the last modification user of the report.
In all cases, I would strongly suggest to always check-in/commit when you deploy a report.
If you want to download several reports from the report server, then you could use a tool like RSScripter for example.
In visual studio 2012, I create new report server projects using the default template below:
When the project is created, it specifies the following build/deployment settings in the configuration:
Obviously these settings are not appropriate for my environment, so I find myself changing them manually every time I create a new report server project.
Is there any way I can change these settings in the default project template so that they will be automatically populated whenever I create a new report?
EDIT: I tried what Reed suggested, but the option was greyed out. Does this indicate that BI projects don't support default templates? If not, how can I create a new custom template for a report server project?
You should be able to create a custom project template for VS 2012 with these defaults modified.
It depends on your environment and your workflow. The below is my personal preference and is a potential solution to your issue:
I tend to use a single report project solution for all my SSRS development, but only for the reports being worked on at that time. It contains all the shared datasets I use for live and test environments and all other settings are as I need.
When ready for deployment, I move the rdl into source control and deploy from there, deleteing the rdl from the project in the process. This helps to keep syncronisation between live reports, source control and filesystem.
In my experience, its far too easy for someone to accidentally modify and deploy an older version of a report from a shared directory.
It will enable you to have the settings you need when you create a new report, as you will not be creating another solution.
i have some Db steps (attach database, adding and configure a new login, configure roles) and i want to automize it using installation package. Right now in project we are using standard Visual studio installer. Can i implement db steps using standard visual studio intaller (custom actions or something else)? Or maybe i should use some others installers like Install shield, Wix?
As far as I know Visual Studio setup project doesn't offer this functionality out of the box (although, my experience with it is tiny). Also, it is not a good idea to implement it all from scratch in a custom action - it is really the last resort.
Other vendors, at least those you mentioned, do offer this. if you decide to move to one of those, keep in mind the learning curve, which will take some of your time (for WiX is probably more). However, if the VS setup project is quite small and simple, it might be a good idea to move at this point, considering the fact that VS setup project type was deprecated by Microsoft.
For DB configuration you may create SQL script which can be installed with an application or into temp directory and feed it to whatever consumes sql scripts in mssql (in oracle its sqlplus). Not sure about visual studio but that's how I saw in one project for InstallShield.
I'm setting up an automatic deployment scheme. It would be really handy for us if we could put older msis on the server and have all the clients roll back to previous versions if one of our new releases turns out to be too bug riddled.
Right now, the msi is bitching at me "Unable to install because a newer version of this product is already installed". What kind of property can I set to turn this behavior off? I will gladly do so in my post build vb script.
Thanks
Isaac
Are you using a group policy on your
domain to deploy the msi?
Do you have
a setup project for your msi in
Visual Studio?
Anyhow, I see a solution but not sure if that's right for you...
You need the code matching the old msi that you want to deploy back.
Open the solution matching the code of the old msi.
Using <F4>, open the properties window of the setup project matching the msi,
Increment the Version to a higher number then the one currently deployed. It will ask if you want to change the product code, click Yes.
Rebuild the setup project then deploy.
Since the built msi has a higher version number, it will update the one deployed.
I solved this by changing the DetectNewerInstalledVersion property to false.
It doesn't bitch anymore about this.
Now, with the script that sets the REINSTALLMODE to amus and this setting, my msi will overwrite anything regardless of version.
Using VB6
I want to setup the Project, Last time I used VB 6 Package and Deployment wizard. It asks to modify some system file. I modified my system file, and then it worked. Now again I want to setup my new project, is asking to change the system file.
Once I set up the project, is asking to change the system file and crystal report files (like crystl32.ocx… etc)
Is showing error like, “out of stack space”, “out of system date” etc...
Why is always asking to change?
What is best way to setup a vb project? If there is any software is available for setup a project.
Always am getting a problem for setup a VB 6 project, please Can any one help to solve my problem?
I've been using Advanced Installer (for VB.NET projects, but that doesn't matter), the free version is very capable and easy to use.
But to answer your question, sounds like the package wizard has got itself in a bad state. I'd re-install VB6 in that case.
In my experience the VB6 Package and Deployment wizard is pretty useless. I recommend you look at commercial installation software like InstallShield or Wise.
If you have Visual Studio 2002 or above, you could also try hacking a .NET setup project to install your VB6 components. It is capable of self-registering COM binaries, creating Start menu shortcuts, etc.
Have a look at the answers to these questions
What is the best simple install system [for VB6 programs] on Windows XP and Vista
What is the best choice for building windows installers
Do you have a copy of Visual Studio? You can use that to create installers instead.
You may use some other thirdparty software like installshield to create the setups. As far as I see they are much flexible.
Wise installer is one of other similar products.
Microsoft is now offering a replacement for the Package and Deployment Wizard that may help you out. Visual Studio Installer