Squirrel.windows: Squirrel namespace not available in .NET Core

[chrishanzlik]

Squirrel version(s)
2.0.0 and 1.9.1

Description
The Squirrel namespace is not available, after squirrel.windows was installed.

Steps to recreate

mkdir testapp
cd testapp
dotnet new wpf
dotnet add package squirrel.windows --version 2.0.0
dotnet build

Open the project with VS2019 and try to access the namespace.

Actual behavior
Cannot access Squirrels namespace.

[dakahler]

I've been using 1.9.0 on .net core due to this problem, and it's working well. Not sure what's causing it, though!

[chrishanzlik]

@dakahler The problem with 1.9.0 is, that this version has its own Splat reference which forces a downgrade in my current app.

I got the latest version working with .NET Core using a little trick. I created a "Proxy project" which targets .NET Framework. This one will include Squirrel and expose all UpdateManager methods through its own helper class. The project can be consumed without problems by a .NET Core app.

Nevertheless it would be nice to know why the namespace is not available by default.

[GeertvanHorrik]

We wrapped the executable for our .NET Core implementation. You can find it here as a reference: https://github.com/WildGums/Orc.Squirrel/blob/develop/src/Orc.Squirrel/Services/UpdateService.cs

The exe wrapper works as good as calling the libs, and we no longer need to update references for updates to Squirrel (you can independently update Squirrel in your infrastructure only).

[meJevin]

Bump! WPF application on .NET Core 3.1 and with Squirrel.Windows 2.0.0 does not see the namespace. However, with older versions this problem is absent. Can we investigate on this?

[meJevin]

@GeertvanHorrik, can we investigate this?

[GeertvanHorrik]

I am happy to look into this, but I have another PR (#1656) open and would like to see that one closed first.

[GeertvanHorrik]

I am happy to look into this. I don't really need this feature myself but happy to contribute.

Interested in a deal that helps out all of us? If so, then either support @anaisbetts (preferred) for her hard work on Squirrel or me and I'll implement this.

[GeertvanHorrik]

GitHub sponsoring / open collective (if Squirrel has one) / etc would be great. It's a way to show appreciation for the hard work being done by others.

[consultorcva]

@dakahler The problem with 1.9.0 is, that this version has its own Splat reference which forces a downgrade in my current app.

I got the latest version working with .NET Core using a little trick. I created a "Proxy project" which targets .NET Framework. This one will include Squirrel and expose all UpdateManager methods through its own helper class. The project can be consumed without problems by a .NET Core app.

Nevertheless it would be nice to know why the namespace is not available by default.

Hi, could you please a little sample o give me more details. Thanks!

[chrishanzlik]

Hi, could you please a little sample o give me more details. Thanks!

Add a new library to your solution, which is targeting the old .NET Framework (.NET Framework 4.7 for example). Add Squirrel as NuGet dependency, then paste these classes.

In your main project add a reference to this project and use the proxy UpdateManager class.

This works for me at this time.

[JackB-WAI]

Same issue here, had to downgrade to v1.9.0 on a project.