V3 pre release - VS2026

I try a new solution with a simple blink app on Fez Feather. All is working.
I try to rebuild and redeploy (with no change in code !) :
Output window says:

Looking for a device on transport 'USB'.
Found device port 'USB' with ID '258cf303-268c-469d-b870-b2ffd41b6d1d' for transport 'Usb'.
Starting device deployment.
Attempting to connect to device 'USB:SC20100': iteration 0.
Opening port '\\?\usb#vid_1b9f&pid_5010#8&29636e62&0&1#{c13bcfe9-5e84-4187-9baa-45597ffcbb6f}'.
Attaching debugger engine.
Debugger engine attached.
Generating device specific assemblies.
Could not deploy the application. Clean the build and try again

Errors list says:

Assemblies seem good with TinyClr Config:

What can I do ? :face_with_raised_eyebrow:

I wonder if there is an issue with locale and non-english setups. We will check more on our end but let us know if you get it to work.

Did you update the firmware on your device to v3?

Close C# and reopen it, then clean and rebuild the solution.

If the issue still persists, please take a screenshot of the Solution Explorer window showing the installed NuGet packages. I suspect there may be an exclamation mark icon indicating a problem. You can also try uninstalling that NuGet package and installing it again.

If you can provide the exact steps to reproduce the issue, please share them with us.

Yes, I did. The first time I build and deploy, it’s working.

It could be. I have a french version of VS2026.

You are right ! (as usual :wink:) :


But uninstalling and reinstalling was not better :cry:

I can send you the projects if you prefer ?

Yes, please send it to us if you’re comfortable. We’d like to understand how you were able to install the same NuGet package twice.

It’s sent. I hope you will find …
No ! You’re GHI: you always find :wink:

1 Like

Where did you send it? I haven’t seen any thing yet

@Dat_Tran : we are sunday :thinking:, I don’t want you kill your time.

On support at ghi… (I don’t know if I can put email address here ?)
I can send you elsewhere if you want : [ghi removed]

I can see the link, but it seems I can’t access the .fr site from here in the USA. I also removed your link because it appears to be a private project.

Lastly, please send it directly to me at dat.tran@gh…com. I can review it much faster than messages sent to support@.

1. What’s happening

There are two ways Visual Studio can keep track of NuGet packages in a project:

  • packages.config — the classic way, and the one the TinyCLR templates are built for.
  • PackageReference — Your VS set this option as default.

Currently, TinyCLR OS 3.0 supports packages.config but does not fully support PackageReference yet. We will look into this next version.

2. Temporary fix

You can switch the default to packages.config easily, as shown in the attached image.

You could edit the .csproj to convert it to packages.config, but since this is a simple project, it’s easier to just create a new project from the TinyCLR template and copy your sources into it. Just need to switch to “packages.config” as default before creating new project then VS will take care the rest when adding the nugets.

I don’t have hardware available to verify what I am seeing for now, but after checked your project, I don’t see any other reason yet. Just try it and share the result to us.

Thanks for sharing issue here.

1 Like

With major releases, I would always start a new project and move my sources. Using old projects is always a bad idea

I change Default package management format in Packages.config. Recreate a project. Run it. Close solution ans VS2026, reopen it, and all is working. It’s the good reason ! You’re right (as usual :wink:).

To got further, I check in VS2022, and Packages.config config is set. I suspect I have set it years ago, but can’t remember I did it. Maybe it could be a good idea to remember it in " Build your first project" or in " What you’ll need" page of new docs as it is not a default settings of VS2026 ?

Thanks for pointing it and for helping !

1 Like

It wasn’t an old project, I have started a new project (but as @Dat_Tran pointing it, VS2026 default settings was the cause of the pb).

I believe the default is packages.config. But still we should look into handling this better.

Thanks for the help.

Your welcome ! I asked a question and get Thanks ??? :thinking: It’s a wonderful world. Thanks to you @Gus_Issa and @Dat_Tran.

I believe the default is packages.config in VS2022, but I just install VS2026, maybe default values have changed ?

1 Like

I attempted to add the Tinyclr 3.0 extension to Visual Studio 2026, which was running in a virtual machine. However, when I searched in the extension manager, nothing appeared.

Next, I tried to manually install the extension after downloading it. Unfortunately, I couldn’t do it because the extension couldn’t find a compatible Visual Studio version to install on. What?

Of course, I didn’t fully describe my environment. I’m running on a Mac with an ARM64 chip, and I’m using the ARM64 version of Windows 11. Visual Studio 2026 works perfectly on my system.

Should the 3.0 Tinyclr extension be compatible with an Visual Studio 2026 ARM64 environment?

I suspect TinyConfig might also be an issue.

This is not an issue for me. I have an Intel machine that I’ll configure tomorrow.

Just found this in the documentation:

  • Visual Studio 2026 (any edition including Community) is the supported IDE for the v3 extension — and v3 also adds Visual Studio Code support via a dedicated extension. Both run on Windows only.

@Mike did v2 work for you before?

I never tried V2 with a ARM VM.

it is Windows so the ARM chip may be limiting visibility in the extension manager. I am not seeing any extensions.

*** I just tried to install the V3 extension into Visual Studio Code running natively on a Mac and the installation was successful. I have not tried a project yet.

1 Like

We found out root cause. We have only

<ProductArchitecture>amd64</ProductArchitecture> 

so arm64 can’t detect the extension.

Added.

<ProductArchitecture>arm64</ProductArchitecture>

Thank for sharing issue.

1 Like