iopvs.blogg.se

1. #VB NET 2010 HOW DO I COPY A PROJECT TO NEW MACHINE INSTALL#
2. #VB NET 2010 HOW DO I COPY A PROJECT TO NEW MACHINE 64 BIT#
3. #VB NET 2010 HOW DO I COPY A PROJECT TO NEW MACHINE UPGRADE#
4. #VB NET 2010 HOW DO I COPY A PROJECT TO NEW MACHINE DOWNLOAD#

#VB NET 2010 HOW DO I COPY A PROJECT TO NEW MACHINE UPGRADE#

To upgrade your references, first take a screen shot of your existing assemblies:ĭelete them all unless they point to the latest version. CR runtime is configured for your application platform and not the OS. Now change your Framework version to 4.7.2:Īnd the platform to either x86 or 圆4, it’s on the Build* list. You have the option to backup, I suggest making a copy first and not making a backup, but it’s up to you how you manage the old and new versions. Open your Project, in this instance the app was created in VS 2010 and now opening in VS 2019: NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win64_圆4 NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dotnetĬ:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for. NET tab or Extensions when adding them to your project, much cleaner:Ĭ:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for. You will find the CR dll’s here, I recommend using the. Now that you have the runtime updated here is an example of what you may run into. On rare occasions you may want to re-boot your PC, sometimes the runtime is “locked” and a reboot is required to finish the update.

#VB NET 2010 HOW DO I COPY A PROJECT TO NEW MACHINE INSTALL#

Use the MSI’s ONLY for distribution, not required to be install on your Development PC.Īlso not recommended using the MSI’s because the MSI’s will not integrate into Visual Studio, no CR Projects are available in the Project Wizard.

#VB NET 2010 HOW DO I COPY A PROJECT TO NEW MACHINE 64 BIT#

At the end of the install it prompts to install the 64 bit runtime, click OK. Run the SP 29 EXE to integrate into Visual studio by right clicking on the EXE and selecting Run as Administrator, this is must due to Windows security and to properly register the COM dll’s and Registry Keys we create. VS 2008 will not use CR for VS, you need to upgrade to VS 2010->2019. You can still have CR 2008 and previous but CR for VS can only have one version (13) installed.

and any other CR runtime, no longer required. Uninstall the 64 bit first and then the main package last. Note: the runtime… (64-bit) is an option when installing CR for VS, last step. Uninstall any older MSI’s and the EXE installed on your Development PC, in the screen shot below I have updated already: Note: Version 13.0.xxxx.x can no longer access BusinessObjects Enterprise Servers, you need to use the BOE. NET runtime with CR Designer, ALL runtime for CR 2011 and above is CR for VS Note: As of CR 2011 we no longer install the.

#VB NET 2010 HOW DO I COPY A PROJECT TO NEW MACHINE DOWNLOAD#

If your original project is using CR SPxx runtime, then the first thing you need to do is download the latest SP which you can get from here If upgrading from CR 2008 runtime, note the runtime is no longer in the BusinessObjects folder. NET projects Uninstalling the previous version Note: see this Blog for upgrading BOE, CRS, CRS (OEM). Visual Studio does not do a complete upgrade of the CR Assemblies.ĬR for VS minimum Framework version is based on the version noted: When upgrading existing project to the latest CR for VS runtime there are a few things you need to do after first opening your project. To assist Project Developers upgrading an older project with the latest Service Packs of Crystal Reports for Visual Studio.