Issues with "\cs-script-4.13.1.0" samples

[maettu-this]

Trying to further analyze and eventually fix or work around #434, I have tried to build and run the given sample projects using the latest Visual Studio 2022 (17.14.25). However:

"\cs-script-4.13.1.0\src\CS-Script.sln"

• The current Visual Studio version does not support targeting .NET 10.0. Either target .NET 9.0 or lower, or use Visual Studio version 18.0 or higher

"\cs-script-4.13.1.0\src\CSScriptLib\CSScriptLib.sln"

This solution seems outdated.

"\cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (CodeDom)\Client.NET_Framework (CodeDom).csproj"

"\cs-script-4.13.1.0\src\CSScriptLib\src\CSScriptLib\bin\Debug\netstandard2.0\CSScriptLib.dll" of course couln't be found. After copying it from "\CS-Script.4.13.1\lib\netstandard2.0" there are still several dependency issues, and:

"\cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\Client.NET_Framework (Roslyn+CodeDom).csproj"

After adjusting all <HintPath>..\..\..\packages to <HintPath>packages and Include="..\..\..\packages to Include="packages, still:

NuGet Package restore failed for project Client.NET_Framework (Roslyn+CodeDom): Could not find a part of the path '\cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\Microsoft.CodeAnalysis.Analyzers.3.3.4\buildTransitive/config/analysislevelmicrosoftcodeanalysiscompatibility_2_9_8_default_warnaserror.globalconfig'.. Please see Error List window for detailed warnings and errors.

And several error messages like:

Found conflicts between different versions of "System.Collections.Immutable" that could not be resolved.
There was a conflict between "System.Collections.Immutable, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" and "System.Collections.Immutable, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
    "System.Collections.Immutable, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was chosen because it was primary and "System.Collections.Immutable, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was not.
    References which depend on "System.Collections.Immutable, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" [\cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\System.Collections.Immutable.8.0.0\lib\net462\System.Collections.Immutable.dll].
        \cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\System.Collections.Immutable.8.0.0\lib\net462\System.Collections.Immutable.dll
          Project file item includes which caused reference "\cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\System.Collections.Immutable.8.0.0\lib\net462\System.Collections.Immutable.dll".
            System.Collections.Immutable, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL
            Microsoft.CodeAnalysis, Version=4.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
            Microsoft.CodeAnalysis.CSharp, Version=4.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
            Microsoft.CodeAnalysis.CSharp.Scripting, Version=4.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
            Microsoft.CodeAnalysis.Scripting, Version=4.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
        \cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\Microsoft.CodeAnalysis.Common.4.8.0\lib\netstandard2.0\Microsoft.CodeAnalysis.dll
          Project file item includes which caused reference "\cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\Microsoft.CodeAnalysis.Common.4.8.0\lib\netstandard2.0\Microsoft.CodeAnalysis.dll".
            Microsoft.CodeAnalysis, Version=4.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
        \cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\Microsoft.CodeAnalysis.CSharp.4.8.0\lib\netstandard2.0\Microsoft.CodeAnalysis.CSharp.dll
          Project file item includes which caused reference "\cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\Microsoft.CodeAnalysis.CSharp.4.8.0\lib\netstandard2.0\Microsoft.CodeAnalysis.CSharp.dll".
            Microsoft.CodeAnalysis.CSharp, Version=4.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
        \cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\Microsoft.CodeAnalysis.CSharp.Scripting.4.8.0\lib\netstandard2.0\Microsoft.CodeAnalysis.CSharp.Scripting.dll
          Project file item includes which caused reference "\cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\Microsoft.CodeAnalysis.CSharp.Scripting.4.8.0\lib\netstandard2.0\Microsoft.CodeAnalysis.CSharp.Scripting.dll".
            Microsoft.CodeAnalysis.CSharp.Scripting, Version=4.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
        \cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\Microsoft.CodeAnalysis.Scripting.Common.4.8.0\lib\netstandard2.0\Microsoft.CodeAnalysis.Scripting.dll
          Project file item includes which caused reference "\cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\Microsoft.CodeAnalysis.Scripting.Common.4.8.0\lib\netstandard2.0\Microsoft.CodeAnalysis.Scripting.dll".
            Microsoft.CodeAnalysis.Scripting, Version=4.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
    References which depend on or have been unified to "System.Collections.Immutable, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" [C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\PublicAssemblies\System.Collections.Immutable.dll].
        \cs-script-4.13.1.0\src\CSScriptLib\src\CSScriptLib\bin\Debug\netstandard2.0\CSScriptLib.dll
          Project file item includes which caused reference "\cs-script-4.13.1.0\src\CSScriptLib\src\CSScriptLib\bin\Debug\netstandard2.0\CSScriptLib.dll".
            \cs-script-4.13.1.0\src\CSScriptLib\src\CSScriptLib\bin\Debug\netstandard2.0\CSScriptLib.dll
        \cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\System.Reflection.Metadata.8.0.0\lib\net462\System.Reflection.Metadata.dll
          Project file item includes which caused reference "\cs-script-4.13.1.0\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\packages\System.Reflection.Metadata.8.0.0\lib\net462\System.Reflection.Metadata.dll".
            System.Reflection.Metadata, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL
            Microsoft.CodeAnalysis, Version=4.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
            Microsoft.CodeAnalysis.CSharp, Version=4.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
            Microsoft.CodeAnalysis.Scripting, Version=4.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL

Error messages like this are exactly the same that I get when running my host app.

Summarizing:

• I haven't been able to build nor run any of the CS-Script samples out-of-the-box.
• I haven't been able to build nor run any of the CS-Script samples after trying several modifications to the projects.
• I have been able to build my .NET 4.8 Framework host app :-)
• I haven't been able to let my .NET 4.8 Framework host app successfully compile a script with CS-Script 4.11.2.0 (not 4.13.1.0 because of #/share compiler flag causes CS2007 error after upgrading to 4.13.1 #435)

People like us don't give up that quickly. So I am still convinced it will work eventually. Still, I highly appreciate your advice and improvements to the next CS-Script releases!

(And I now even better understand that with .NET 5+ the dependency handling didn't get easier at all...)

[oleg-shilo]

People like us don't give up that quickly. ...

Great, then we can definitely get there. :o)

After observing the challenges you are facing, I came to the conclusion that I will need to add a dedicated wiki for describing the use cases you shared with me. I will start doing it on the weekend. But until it's ready, I will try to support you directly via issues' discussions.

That /share fix will be published tomorrow, so it will no longer be a problem.

As for the dependencies... You used the phrase like "I need to understand the dependency handling."
I feel that your challenges can be solved more easily than they seem. There is no much dependency handling. Sorry if I am oversimplifying.

The CS-Script codebase is developed on the latest .NET and the latest VS version. The CS-Script artifacts can be used on older versions (.NET8) as well, but if you want to build them (e.g. to run the samples) then you need to use .NET 10 (e.g. VS 2026). This will address the very first and the second problem (text in bold).

The third and the forth one are the result of trying to continue without the primary cause being addressed.
If you have VS2026 or even VS2022, but with .NET10 SDK, then you can build all solution projects, including the samples.

I just rebuilt the whole solution in VS2022. All good.

After adjusting all ..

The user should never modify the project file for CS-Script to build. It's all caused by the first problem.

All this is somewhat similar to the other problem you raised in this repo - Microsoft.Code analysis.

If you just add cs-script packageto your host application, it will have ALL dependencies it needs. You do not need to know how to "handle dependencies". But since you wanted to maintain two versions of shared transient packages, that became more challenging. And it also stopped being a CS-Script issue but rather a canonical .NET compatibility problem that has no good solution, except updating to the latest package version.

On top of that, you tried removing some of the assemblies from the deployment. That makes the whole picture even more complicated. And while I am happy to give you a few hints, I cannot put this sort of recommendations in the product documentation as they deviate from the standard .NET practices.

Anyway, let's start with installing .NET SDK. This should at least give you a proper baseline.

[oleg-shilo]

I wasn't satisfied, so I tested a freshly cloned copy of the repository, and indeed, I see some build problems. I would like to resolve them first before I accidentally mislead you.
Please give me a day or two to look at it.

[oleg-shilo]

Please try now.
I found that CSScriptLib was embedding the .net9 resource (build.dll) that is no longer part of the built. Currently .NET8 and .NET10 targets are built. Though I do not believe it is related to the problem you are experiencing. But you still need to get the latest repo to build it after you install .NET10 SDK.

This resource is planned for removal and is not used anymore (it's a legacy build server).

[oleg-shilo]

I have also added in this thread the samples for the use cases that I think you are trying to implement: #434 (comment)

[maettu-this]

I have installed VS2026, need it soon anyway. Here's the findings with the latest \cs-script-4.13.2.0 source:

"\src\CSScriptLib\CSScriptLib.sln"

• When loading the solution, still:
  \src\CSScriptLib\src\CSScriptLib.Client\CSScriptLib.Client.csproj : error : The project file cannot be found.
  \src\CSScriptLib\src\CSScriptLib.Client461\CSScriptLib.Client461.csproj : error : The project file cannot be found.

"\src\CSScriptLib\src\CSScriptLib\CSScriptLib.csproj"

• When trying to build in VS2026:
  MSB3103 Invalid Resx file. Could not find a part of the path '\src\BuildServer\out\net10.0\build.dll'. Line 124, position 7. CSScriptLib \src\CSScriptLib\src\CSScriptLib\Properties\Resources.resx 124

"\src\CS-Script.sln"

Loading this solution works without issues.

"\src\CSScriptLib\src\CSScriptLib\CSScriptLib.csproj"

• When trying to build in VS2026:
  Error signing output with public key from file 'sgKey.snk' -- File not found.
• And 2 warnings:
  Unable to locate repository with working directory that contains directory '\src\CSScriptLib\src\CSScriptLib'.
  Source control information is not available - the generated source link is empty.

"\src\CSScriptLib\src\Client.NET-Framework (Roslyn+CodeDom)\Client.NET_Framework (Roslyn+CodeDom).csproj"

• When trying to build in VS2026:
  Error signing output with public key from file 'sgKey.snk' -- File not found.
  Metadata file '\src\CSScriptLib\bin\Debug\netstandard2.0\CSScriptLib.dll' could not be found
• And the same 2 warnings:
  Unable to locate repository with working directory that contains directory '\src\CSScriptLib\src\CSScriptLib'.
  Source control information is not available - the generated source link is empty.

Tomorrow, I'll try to remove the 'sgKey.snk' requirement and try again.

"\src\Client.NET-Framework (CodeDom)\Client.NET_Framework (CodeDom).csproj"

• packages.config is missing:

[maettu-this]

With 'sgKey.snk' requirement removed, building the samples now works in VS2026 :-)

"\src\Tests.CSScriptLib\Tests.CSScriptLib.csproj"

• An error that appears when building:

Error CS0122 'CSScriptException' is inaccessible due to its protection level Tests.CSScriptLib \src\Tests.CSScriptLib\Evaluator.Api.Test.cs 37

"\src\CSScriptLib\src\CSScriptLib\Properties\AssemblyInfo.cs"

• Another minor, the order of comments and code got mixed at some point:

// The following GUID is for the ID of the typelib if this project is exposed to COM

// Signed with sgKey.snk
// The key is published in the repo according the MS recommendation
// (https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming#create-strong-named-net-libraries)
// ✔️ CONSIDER strong naming your library's assemblies.
// ✔️ CONSIDER adding the strong naming key to your source control system.

[assembly: Guid("7cea89c9-e906-4852-ba40-16be33bcc2d1")]
[assembly: InternalsVisibleTo("cscs.tests, PublicKey=" +
    "0024000004800000940000000602000000240000525341310004000001000100d17b106c0897f2" +
    "962c69449792d3b89ce228b8413184d66934ead688f75e8526ba162c7e6d4a32a48abdccbc8863" +
    "ec9ae6ca453f05d148a968e217a0e22805ce9b5138d3f4f7f004c8074fa7e001c2a3bb0b8c275a" +
    "40967efff2aa574ca04339df8fdcdcb6eb01afa1b28f0ad1d6498d0e17ba555c8c2535c5d6e1e7" +
    "121bd7a0")]

Should probably be:

// The following GUID is for the ID of the typelib if this project is exposed to COM
[assembly: Guid("7cea89c9-e906-4852-ba40-16be33bcc2d1")]

// Signed with sgKey.snk
// The key is published in the repo according the MS recommendation
// (https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming#create-strong-named-net-libraries)
// ✔️ CONSIDER strong naming your library's assemblies.
// ✔️ CONSIDER adding the strong naming key to your source control system.
[assembly: InternalsVisibleTo("cscs.tests, PublicKey=" +
    "0024000004800000940000000602000000240000525341310004000001000100d17b106c0897f2" +
    "962c69449792d3b89ce228b8413184d66934ead688f75e8526ba162c7e6d4a32a48abdccbc8863" +
    "ec9ae6ca453f05d148a968e217a0e22805ce9b5138d3f4f7f004c8074fa7e001c2a3bb0b8c275a" +
    "40967efff2aa574ca04339df8fdcdcb6eb01afa1b28f0ad1d6498d0e17ba555c8c2535c5d6e1e7" +
    "121bd7a0")]

[oleg-shilo]

With 'sgKey.snk' requirement removed, building the samples now works in VS2026

Great, it looks like you found that you need to execute prepare-environment.cmd

I mentioned this in the contribution guideline from the angle "you will need to generate your own certificates". But after seeing your problem, I also added the note about this in the root README.md.

---

The second problem is less obvious. It is a side effect of signing the assembly but not distributing the key. The friend assembly Tests.CSScriptLib.dll stops "being a friend" if not built on my machine. Thank you for bringing it to my attention.

To solve it. I created 3 poplyfils in the test project so you can sync, and it will be OK now.