Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an assembly icon; strange as it may seem, but this resolved the "cannot find AssymblyInfo.fs" error that occurred from time to time #34

Merged
merged 1 commit into from
Oct 16, 2022

Conversation

abelbraaksma
Copy link
Member

@abelbraaksma abelbraaksma commented Oct 16, 2022

It's certainly possible that one is unrelated to another. But when building in Visual Studio 2022, from time to time, a dozen of the following errors occurred:

Error FS0225 Source file 'D:\Projects\OpenSource\Abel\TaskSeq\src\FSharpy.TaskSeq\obj\Debug\net6.0\FSharpy.TaskSeq.AssemblyInfo.fs' could not be found

Even though the project compiled and ran fine. This post hinted at the cause, though I'm fully aware it may be unrelated: https://stackoverflow.com/questions/6494691/source-file-properties-assemblyinfo-cs-could-not-be-found

So, the absence of AssemblyInfo.fs is by design. Though I kind liked the old approach. Anyway, I wasn't the only one surprised by this: dotnet/fsharp#5309

The issue remains though, that the above error appears from time to time, which seems to me like some sort of synchronization bug between the autogenerated file from fsproj and the MSBuild compiler. Let's see if this hack solves it. It is nice to have some icon anyway.

…cannot find AssymblyInfo.fs" error that occurred from time to time
@abelbraaksma abelbraaksma merged commit 9189d17 into main Oct 16, 2022
@abelbraaksma abelbraaksma deleted the add-icon branch October 16, 2022 23:54
@abelbraaksma abelbraaksma added this to the v0.1.0 milestone Mar 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant