Page Comparison

Currently, we are using can use any Visual Studio 2019 to run ARASS such as VS 2019

To create or edit a crystal report, we can use Microsoft Visual Studio 2013/2015/2017, then save the code, then we can continue to use VS2019 to run that crystal report on ARASS

NoteNotes:

-One limitation when working with Microsoft Visual Studio 2015 is that the stdole.dll might be put in the bin folder when build the project in VS2019. The stdole.dll should be removed from the bin folder before moving the deployment to the server.

-Currently, we can not use SAP CrystalReports for Visual Studio 2019 because this Crystal version is not working with the current Crystal Report runtime on the servers (i.e it does not work with CR version22). This can be changed in the future when Crystal Report runtime on the servers can be updated

Software (being used and proved to be working together) Can use VS 2013 or VS 2015 to build Crystal Reports and have to install correspondent SAP Crystal Reports	Install location
Visual Studio 2013 OR Visual Studio 2015	\\Tc4s0a\groups\AARA\AARAD\Software Library\Developer Tools\Microsoft\Visual Studio 2013 (will work with SAP CrystalReports for Visual Studio 2013) \\Tc4s0a\groups\AARA\AARAD\Software Library\Developer Tools\Microsoft\Visual Studio 2015 (will work with SAP CrystalReports for Visual Studio 2017) -->this software is used to edit/view a crystal report
Crystal Reports for VS 2013 OR Crystal Reports (64-bit) for VS 2015	\\Tc4s0a\groups\AARA\AARAD\Software Library\Developer Tools\SAP CrystalReports for Visual Studio 2013 \\Tc4s0a\groups\AARA\AARAD\Software Library\Developer Tools\SAP CrystalReports for Visual Studio 2017. (but I do not find it is working with VS2017) Notes: 2023-05-08: All servers in Prod/Acc/Dev are running SAP Crystal Reports 13.0.22.2668 64 bit. Therefore we need to install an SAP CrystalReport for VS to work with the same version of Crystal Report on the servers: Installing SAP CrystalReports for VS 2017, check the Computer setting->will see the version 22 as same as the crystal report version on the servers Image Added If you find the version is not the same (in this example, it should be 22) Then: Using Setting to remove all SAP Crystal Reports installations Go to net work folder and download the right SAP Crystal Reports (mentioned above) Go to VS-> remove Crystal Report dll and re-add , remember to set Copy property as True Important Note If using Visual Studio 2015 to build crystal reports, we should remove stdole.dll from bin folder in the deployment package before moving that to the servers. Otherwise, the crystal reports will not be opened. The remove is not required when we use Visual Studio 2013.
CLF Dependencies	Fixing CLF Page Plugin or Fixing CLF Page Plugin 1.1 Note: To install StreamTagFilter and CLFPagePlugin, try to pass by command line running as Administrator
CLF Page	This project are using CLF Page \\tcinfomaster\mytcroot\Views\WCMS\en-CA\media\documents\cwms\CLFPage https://tcmarin.atlassian.net/wiki/spaces/OP/pages/76906592/Development+environment+documentation#Set-up-CLFPagePlugin
TCMailer	This project are using the version for TCMailerNet \\Tc4s0a\groups\AARA\AARAD\Software Library\Developer Desktop\Old CLF Files\Old CLF Files\TCMailerNet 2.0
AjaxControlToolkit	Version used: 4.1.50401.0
TOAD	\\Tc4s0a\groups\AARA\AARAD\Software Library\Vendor Software\Toad\Installs

*If you don’t have access to \\TC4S0A\GROUPS\AARA\AARAD\, you need to send an email to Service Desk

ARASS is using the C:\Program Files\Transport Canada folder (not :\Program Files (x86)\Transport Canada?). You can copy the content of C:\Program Files (x86)\Transport Canada to C:\Program Files\Transport Canada

Inside C:\Program Files\Transport Canada, you should have AjaxControlToolkit.dll, CLFPage.dll, TcMailerNet.dll, and the following folders: StreamTagFilter and CLFPagePlugin

• Inside your local .vs, make sure the applicationhost.config contains these lines inside the <modules> section

<modules>
  <add name="StreamTagFilter-2.0" type="Utility.IIS.StreamTagFilterModule, StreamTagFilter.NET.2.0, Version=1.0.5.0, Culture=neutral, PublicKeyToken=d3d707ec692e4024" preCondition="runtimeVersionv2.0" />
  <add name="StreamTagFilter-4.0" type="Utility.IIS.StreamTagFilterModule, StreamTagFilter.NET.4.0, Version=1.0.5.0, Culture=neutral, PublicKeyToken=d3d707ec692e4024" preCondition="runtimeVersionv4.0" />
</modules>

• If you are seeing any exclamation marks in the References for CLFPage , AjaxControlToolkit, TCMailerNet then add their references by pointing to their dll 's locations on C:\Program Files\Transport Canada, and make sure Copy Local is True. When Copy Local is True, then building the solution will add the dll copies to the bin folder.

• If the layout is still not fixed (see image below), this means the CLFPage.dll is not correct (calling the old stylesheets), please see below for the fix.

Go to the bin folder and delete the CLFPage.dll. Go to References and remove the CFLPage.dll.

Copy the correct CLFPage.dll (ask team members) to C:\Program Files\Transport Canada and add the Reference for CLFPage.dll to the path of the bin folder

Change in the web.config:

Commenting this line for CLFVersion

Build the solution and run it. The layout should now be displaying correctly.

If you find this type of error

copy your folder in Program Files(x86) in Program Files