#Ms visual studio 2012 upgrade

Thank you for responding! Since I posted my initial query to you, I've done a lot of work on my own and found an upgrade path for developers moving from VS2008 to VS2012. So I'm wondering if you could give me some guidance about whether VS2012 will just 'work' with the VS2008 Merge Modules or whether problems will arise?Īny insight you could provide would be MUCH appreciated, My module simply generates reports based on the existing templates and what data is currently in SQL Server. No new report templates are ever created by the user. The pertinent References in my Web project are these: Note: In my case I've built my own reporting module which simply makes calls to your various DLLs. Reading through the many comments above I am unclear as to whether the Crystal Reports functionality in my web application will be supported from what will soon be my VS2012 web application. I have been using the Crystal Reports Merge Modules successfully with Visual Studio 2008 for several years now to support the many Crystal Reports templates I've built for a client.įor various reasons I now need to upgrade to Visual Studio 2012. So when our VB.NET app is executed to generate the report, the Crystal Reports methods/properties version of the runtime components are the same as those in the VB.NET app used to run the reports we wrote in CR2011? We would then distribute, to our clients, our reports created in CR2011 as well as the VS2010 (and VS2012) runtime components. for VS2010 in our app to generate our reports.

#Ms visual studio 2012 update

We would update our VB.NET app to VS2010 (and then this 2012 when it is made available). We would upgrade our developers to CR2011. In order to stay up-to-date with Crystal as far as writing/maintaining our reports and then deploying to our clients:

#Ms visual studio 2012 software

We do have a VB.NET app that uses the CR2008 SDK to run/generate the reports through our own non-VB.NET software application. Many of our developers use the Designer to write/edit all of our Crystal Reports. What I was referring to as the Developer edition, is what you refer to as the Designer. Please read to see if I have this correct: I’ll update this post closer to our release with specifics around platform support updates.

#Ms visual studio 2012 windows

In addition to supporting Microsoft Visual Studio 2012, the new release of SAP Crystal Reports will also add support for Windows 8. In turn, that should also make it less confusing for users to decide which version is needed. This allows us to update our offering more quickly as well as maintain fewer versions of the product.

We are dropping the year from our naming convention, since the product will support multiple releases of VS. To reflect support of this 2012 release, we will be renaming our product to SAP Crystal Reports, developer version for Microsoft Visual Studio. You should note that support for Microsoft Visual Studio 2012 will be delivered in an upcoming service pack release, which can be applied to an installation of the current product (SAP Crystal Reports, version for Visual Studio 2010). Dates are of course subject to change, based on product readiness. NET Framework 4.5, with plans to make this update available in late Q1 2013. Our development teams are hard at work updating SAP Crystal Reports to support Visual Studio 2012 and. We’ve received a lot of interest already, so here are some details on how we will support this product. On September 12, Microsoft launched Microsoft Visual Studio 2012.