Closed Xerxes-2 closed 8 months ago
WOW. That is a weird one.
And, wow, your offer I greatly appreciated. Let me have a quick look at and I will be able to guide you.
I found that the problem was not so easy to track but easy to fix so I have just prepared the prerelease for you to test. Why prerelease? It's because of my system the problem also sows but it has slightly different symptoms compared to what you reported. Probably because you are 2 versions behind.
Can you please test the executable in your environment and let me know if it addresses the problem? And then I will promote it in a proper release.
I found that the problem was not so easy to track but easy to fix so I have just prepared the prerelease for you to test. Why prerelease? It's because of my system the problem also sows but it has slightly different symptoms compared to what you reported. Probably because you are 2 versions behind.
Can you please test the executable in your environment and let me know if it addresses the problem? And then I will promote it in a proper release.
The .csx
script works fine now. But css -new test.csx
still create a test.cs
file.
yep, I noticed that too but was fully focused on the compilation. good that I asked you re-test. I will address the creation of the file and rerelease. Cheers, have a good night
Done, you can get the latest release v4.8.5:
dotnet tool install --global cs-script.cli
choco install cs-script
Thank you! The new version works well
Description: When trying to create and run a
.csx
file using the C# Script execution engine, I encountered unexpected behaviour. The.csx
file seems to be treated as VBScript instead of C# script, which leads to compilation errors.My environment:
Reproduce:
css -new test.csx
. This creates atest.cs
file instead oftest.csx
.test.csx
.css test.csx
.Expected Behaviour:
css -new foo.csx
should create a.csx
fileActual Behavior: I receive the following error:
It appears the script is being treated as VBScript rather than C# script.
Offer to Help: I understand that maintainers can be busy, and given that this seems to be a simple fix, I'm more than willing to create a PR to address this issue. However, I would appreciate some guidance on which project or directory I should focus on. If you can point me in the right direction, I'd be glad to assist and contribute to the project.