Autodesk.IDSDK 1.2.11

Autodesk.IDSDK.Client

Overview

This repository contains the source code for the dotnet IDSDK Wrapper.

This project is compiled as a .Net standard 2.0 library.

Runtime requirements

IDSDK 1.20.0 and later require the Visual C++ 2015-2022 redistributable 14.38 or newer (msvcp140.dll 14.38+).

The native AdskIdentitySDK.dll in these versions uses the constexpr std::mutex construction introduced in Visual Studio 2022 17.10. On a machine with an older msvcp140.dll, the first call that takes a lock — including Client.Init — fails with an access violation that terminates the host process, rather than returning an idsdk_status_code. The DLL itself loads successfully, so the failure only appears at first use.

Installers that bundle or require a VC++ redistributable must enforce a floor of 14.38 or newer. Note that a newer redistributable installed alongside is not enough if the application directory carries an app-local copy of an older msvcp140.dll — the app-local copy wins at load time.

Relation to Autodesk.NET

This project is being modeled after other Autodesk.NET projects, as the intention is to eventually include this within the Autodesk.NET ecosystem.

Until the project is further developed and refined, it will remain under the desktop-connector organization.

General Autodesk.NET & contributing information can be found at the organisation page.

Inner-sourcing

See the Desktop Connector inner-sourcing wiki for information about contributing to this repository.

Building

In order to build this you will need Visual Studio 2017 Update 3.

Visual Studio

1. Open the solution file Autodesk.IDSDK.Client.sln

2. Verify that the platform is set to Any CPU

3. All Unit Tests should appear in Test Explorer under the project Autodesk.IDSDK.Client.Tests

Command Line

If you want to use the .Net runtime tools, you will also need to install the .Net Core SDK.

1. dotnet restore Autodesk.IDSDK.Client.sln

2. dotnet build Autodesk.IDSDK.Client.sln

3. dotnet test Testing\Autodesk.IDSDK.Client.Tests\Autodesk.IDSDK.Client.Tests.csproj

Branching and Publishing

• All pull requests should be submitted to the develop branch

• Pull requests should consider a change to the version number based on semantic version strategies. The version number is stored in the SolutionAssemblyInfo.tt file. The following rules should be applied:

  • If a pull request is the first edit in develop after an official build, then the version number should be changed. For example, if version 4.0.0 has just shipped, then the next edit will be either 5.0.0, 4.1.0 or 4.0.1 depending on the nature of the change

  • If a pull request is a secondary edit since an official build, then the version number doesn't need to be updated since we haven't shipped this build number yet. The exception is as follows: If the last official build is 4.0.0 and the current version number in the source file is 4.1.0 then that means a feature was added to the library. But since develop hasn't been integrated into master yet, an official build of 4.1.0 has not been created yet. If the secondary edit is one that introduces a compatibility change, then the version number should switch to 5.0.0. Essentially, we are skipping version 4.1.0 - no official build was every done with that version

• When a pull request is approved and accepted, a CI build will kick off that results in a nuget package called Autodesk.IDSDK.Client.[Major].[Minor].[Patch]-alpha-[Number].nupkg in the team-comet-nuget repo. This package is considered to be a pre-release package. It can be consumed for testing purposes but no application should ship with this package

• When a release (non-alpha) build is desired, the develop branch will be merged into master. This will kick off a build automatically