HI:
We are using Visual Studio 2005 to develop an internal web application and using the internal Crystal Report tools to generate a report (Actually a sort of print screen to handle a data intensive page). We are not using the crystal report viewer, again just using the report builder tool to build the report and then converting to a PDF to present to the webpage.
Visual Studio is approved development tool. However just saying the word Crystal scares the heck out of the enterprise architecture review board which I have to go in front of tomorrow. They point to security issues, and changes that Crystal makes to server settings when installing it on the web server.
My argument will focus on the fact that Crystal is now a part of visual studio and is a plug in for the .NET 2.0 framework. If Visual Studio is the approved development tool then this should umbrella into that. I will also add that we are not binding the crystal report to our datasource, but instead are using transfer objects to handle the feed the data to the report so it is completely decoupled from the database. I will finally say that we are not installing Crystal as a stand alone product, but as just a class library that our application can use.
I am looking for advice regarding some of their arguments against using Crystal and some other options they may suggest. My goal is to use Crystal since we have already built the report using it and I would hate to go back. Any suggestions obviously appreciated.
Thanks
-------------------------------------------
Ummm, we have a bit of a problem here....
We are using Visual Studio 2005 to develop an internal web application and using the internal Crystal Report tools to generate a report (Actually a sort of print screen to handle a data intensive page). We are not using the crystal report viewer, again just using the report builder tool to build the report and then converting to a PDF to present to the webpage.
Visual Studio is approved development tool. However just saying the word Crystal scares the heck out of the enterprise architecture review board which I have to go in front of tomorrow. They point to security issues, and changes that Crystal makes to server settings when installing it on the web server.
My argument will focus on the fact that Crystal is now a part of visual studio and is a plug in for the .NET 2.0 framework. If Visual Studio is the approved development tool then this should umbrella into that. I will also add that we are not binding the crystal report to our datasource, but instead are using transfer objects to handle the feed the data to the report so it is completely decoupled from the database. I will finally say that we are not installing Crystal as a stand alone product, but as just a class library that our application can use.
I am looking for advice regarding some of their arguments against using Crystal and some other options they may suggest. My goal is to use Crystal since we have already built the report using it and I would hate to go back. Any suggestions obviously appreciated.
Thanks
-------------------------------------------
Ummm, we have a bit of a problem here....