NuGet package: manual installation

It is always possible to manually install Eyeshot 2024 packages via the Visual Studio NuGet package management page.

This is the only way to install Eyeshot 2024 packages in non SDK-projects or when using Visual Studio 2019 or previous version.


Check the package source mapping

The first thing to check is that it exists a package source correctly mapping the local offline location of the Eyeshot NuGet Packages.

In Visual Studio Select the menu Tools>NuGet Package Manager>Package Manager Settings.

In the opened window, select the Package Source item on the left pane, and check that it exists and is enabled a source named Eyeshot 2024 Local pointing to the folder where the Eyeshot NuGet packages have been installed.

If not, create a new source by pressing the Add button (the green cross in the following picture) and name it accordingly.


Install the Eyeshot NuGet Package

Once the package source is correctly set, it is possible to install the Eyeshot packages.

In the Solution Explorer panel, right click on the References item of the wanted project, then click on Manage NuGet Packages...

This will open the NuGet packages management page for the project: check that the package source is correctly set to Eyeshot 2024 Local (if not, select it from the selection combo box), go to the Browse tab and then select and install the wanted NuGet package.

You have to install one of the following packages:

  • devDept.Eyeshot: install this package for a console application project;
  • devDept.Eyeshot.Control.Win: install this package for a Windows Forms application project;
  • devDept.Eyeshot.Control.Wpf: install this project for a WPF application project.

If you plan to use the ReadAutodesk or WriteAutodesk classes, you have to also install an additional package:

  • devDept.Eyeshot.x64: install this package to manage DWG/DXF files for x64 projects;
  • devDept.Eyeshot.x86: install this package to manage DWG/DXF files for x86 projects;


Using the devDept NuGet Server

Through the devDept NuGet Server users can easily include the Eyeshot packages and update to the latest official version.

The following steps will demonstrate how this can be done in Visual Studio:

1. Navigate to the Package Manager Settings menu.

2. Add a new source in the Package Sources section

3. In the Source field fill the address of the devDept NuGet Server and click Update.

4. The devDept Server is added and ready to use. Click on the Manage NuGet Packages menu.

5. Set the devDept Server as a package source. Enter user credentials (from your devDept account) when prompted and search for the needed package.


Resetting the devDept NuGet Credentials

If you want to reset the cached credentials from Visual Studio, follow these steps:

1. Delete the Package Source.

2. From "Control Panel" > "User Accounts" > "Credential Manager" > "Windows Credentials," delete the two entries related to devDept.

If that's not enough, make sure to close all instances of Visual Studio and also delete the v3-cache folder located in %AppData%..\Local\NuGet.


Beta and nightly releases

Following NuGet guidelines, to install a beta or nightly release, you must enable the 'Include prerelease' option.


Was this article helpful?
2 out of 2 found this helpful


Date Votes
  • First of all, sorry for cross-posting a related question here , but I thought it might help others in similar situations.

    We're building our application in a CI/CD pipeline on Gitlab at the moment. This change (...This is the only way to install Eyeshot 2024...) seems to imply that we won't be able to build our app anymore unless we somehow manage to get these nuget packages hosted on a location that's accessible by our CI build process... 

    It would be very nice if there would be a way for us to make use of some kind of public nuget resource to download our packages from, instead of having to rely on locally distributed packages. For example: DevExpress uses a hosted nuget repository that is accessible for any customer with a license by using a private api endpoint based on a unique key. Could this be an option somewhere in the near future?

    If not, what would otherwise be the recommended way to do CI builds of applications using the EyeShot component? 


  • Hi Gert,

    we're currently working on setting up a private NuGet server, so as soon as it will be ready you shouldn't have any problem with your use case.

    We will keep you all updated with an official announcement, as soon as any news is available.
    In the meantime, we are deploying Eyeshot as usual with a setup, and the NuGet packages are installed with it. 

  • Hi Frederico,

    Thanks for your quick answer. Does "In the meantime" extend into the release window of the 2024 version too?

  • Hi Gert,

    as you can see, now the devDept NuGet server is up and running: you could follow the updated info of this article, in order to set it up and perform the first tests on your side.
    Please, feel free to share your feedback: they will be very helpful.

  • WOW! That was insanely fast! Very impressive :)

    First observations:
    - The repository currently shows only the 2024.0.73 version, marked as stable. Does this mean it is not in BETA anymore?
    - Will I be able to access the current 2023 version on this repository too in the future? (this would make testing easier, because it won't require me to update my app first)

  • Hi Gert,

    Thank you so much for your feedback!

    - Starting from the next beta release, the beta packages will be correctly marked as prerelease (we just updated this article too).
    - Regarding the 2023 version, currently, there are no plans to publish packages for it. However, we'll reassess this decision after gathering more feedback during the Beta period.


Please sign in to leave a comment.

Articles in this section

See more