CADViewer implementation of dotNet Core controllers
The repository contains a full setup of CADViewer with CAD Converters and script controllers for dotNet Core.
1: CADViewer script library - in its preferred folder structure
2: AutoXchange AX2022 Converter and DWG Merge 2022 Converter - in their preferred folder structure
3: All structures for file-conversion, sample drawings, redlines, etc.
4: A number of HTML files with CADViewer samples.
5: The folder structure for dotNet Core script handlers for communication between CADViewer and the back-end AutoXchange 2022.
6: The converter folder structure contains a larger set of fonts, installed in /cadviewer/converters/ax2022/windows/fonts/, but a fuller set of fonts can be installed.
Read the sections on installing and handling Fonts in AutoXchange 2020 TechDocs and TroubleShooting.
1: Install into a folder of choice
2: If different from default install folder, then locate appsettings.json and modify paths and urls to match your server settings.
3: If different from default install folder and url, in the folder cadviewer/wwwroot/html update the JavScript variables:
var ServerBackEndUrl = "https://localhost:44374/";
var ServerUrl = "https://localhost:44374/";
var ServerLocation = "";
The variable ServerLocation is used to set another server path for the installation. This should only be done in testing. It is normally kept empty and settings in appsettings.json are used. ServerBackEndUrl is not used for dotNetCore unless the back-end CADViewerController.cs is accessible from a different url/port in which also appsettings.json needs to be updated.
4: The method cvjs_setAllServerPaths_and_Handlers() sets the front-end and back-end combination as well as the controlling paths. Note that the last parameter in this method is the controller name. If the controller name variable is undefined or "", then the back-end location must be the url of the end-point itself, so: ServerBackEndUrl = "https://localhost:44374/CADViewer" in this case.
// Pass over the location of the installation: will update the internal paths, as well as front-end and back-end platforms
// last parameter is the controller name , ServerBackEndUrl+controller = controller path
cvjs_setAllServerPaths_and_Handlers(ServerBackEndUrl, ServerUrl, ServerLocation, "dotNetCore", "JavaScript", "floorPlan", "CADViewer");
5: Once installed, run cadviewer.sln, the HTML samples under /cadviewer/wwwroot/html/ can be accessed from a web-browser. Use http://localhost:xxxxx/cadviewer/html/CADViewer_fileloader_670.html as a starting point (assuming that your have installed under http://localhost:xxxxx).
This repository should contain the latest converters, but in case you need to update any of the back-end converters please follow:
-
Download AutoXchange (and other converters), install (unzip) AX2020 in cadviewer/converters/ax2020/windows or cadviewer/converters/ax2020/linux or in the designated folder structure.
-
Read the sections on installing and handling Fonts in AutoXchange 2020 TechDocs and TroubleShooting.
-
Try out the samples and build your own application!
For a CADViewer dotNetcore installation on Windows, the base file-structure should be as below: CADViewer and AutoXchange is included in this repository, but it can be recreated by downloading the components directly from: https://cadviewer.com/download
c:\cadviewer-testapp-dotnet-core-01\cadviewer\cadviewer\
└─── wwwroot
├── app
│ ├── cv
│ │ ├── cv-pro
│ │ │ ├── menu_config
│ │ │ ├── language_table
│ │ │ └── space
│ │ │ ├── css
│ │ │ └── html
│ │ ├── cv-core
│ │ │ ├── menu_config
│ │ │ └── language_table
│ │ └── cv-custom_commands
│ ├── fonts
│ ├── images
│ ├── js
│ ├── css
│ └── user_resources
├── converters
│ ├── ax2022
│ │ ├── windows
│ │ │ └── fonts
│ │ └── linux
│ │ └── fonts
│ ├── dwgmerge2022
│ │ ├── windows
│ │ │ └── fonts
│ │ └── linux
│ │ └── fonts
│ ├── linklist2022
│ │ ├── windows
│ │ │ └── fonts
│ │ └── linux
│ │ └── fonts
│ └── files
├── content
├── html
└── temp_print
Note that folders for controller configuration are set as part of the dotNet core main project
In folder:
c:\cadviewer-testapp-dotnet-core-01\cadviewer
└─── cadviewer
└── appsettings.json
locate the configuration file: appsettings.json , edit the key settings that controls Converter and CADViewer paths to reflect your installation.
In folder:
c:\cadviewer-testapp-dotnet-core-01\cadviewer
└─── cadviewer
└─── Controllers
└── CADViewerController.cs
The file CADViewerController.cs contains the controllers that CADViewer uses to manipulate content on the server and to control CAD conversion.
In folder:
c:\cadviewer-testapp-dotnet-core-01\cadviewer
└─── cadviewer
└── html
identify your sample mysample.html file, and ensure that it correctly sets the ServerLocation and ServeUrl parameters
Open a web-browser pointing to your sample html file: http:/localhost:44374/html/mysample.html
Use the server traces and browser development console for debugging, alternatively contact our Support
For debugging, the folder:
c:\cadviewer-testapp-dotnet-core-01\cadviewer
└─── cadviewer
└─── wwwroot
└── temp_debug
contains a debug file callApiConversionHandlerLog.txt that lists the command line and traces in the communication with the back-end converter AutoXchange 2020. If drawing files does not display, this file will contain useful information to pinpoint the issue.
One issue that often appears in installations is that interface icons do not display properly:
Typically the variables ServerUrl, ServerLocation or ServerBackEndUrl in the controlling HTML document in /cadviewer/html/ are not set to reflect the front-end server url or port.
var ServerBackEndUrl = ""; // or what is appropriate for my server; used for NodeJS server only
var ServerUrl = "http://localhost/cadviewer/"; // or what is appropriate for my server
var ServerLocation = "c:/xampp/htdocs/cadviewer/"; // or what is appropriate for my server