Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

Manifest resource names are still wrong #50

Closed
funnelweb opened this issue Nov 2, 2012 · 1 comment
Closed

Manifest resource names are still wrong #50

funnelweb opened this issue Nov 2, 2012 · 1 comment

Comments

@funnelweb
Copy link
Contributor

For a resource reference

<EmbeddedResource Include="folder\AAA.xml" />
  • Microsoft F# for MSBuild creates a resource with name

    AAA.xml.

  • The F# in this repository creates a resource with name

    folder.AAA.xml

  • C# in VS2012 creates a manifest resource with name with the project file prepended:

    ProjectName.folder.AAA.xml

No idea why F# differs to C#. We at least have to make the F# buiilds consistent.

@funnelweb
Copy link
Contributor Author

A partial fix for this is here. c7a7580

To quote:

The comments in FSharpBuild/Fsc.fs explain a bit more. It is realy hard to work out how to make this perfectly consistent. Essentially, be careful using resources in folders if you want your projects to be portable across VisualStudio/MSBuild and mono/MonoDevelop/XBuild

We hit this bug in fsharp/fsharpbinding, but we've moved that to no longer use resources in folders for now.

ctaggart pushed a commit to ctaggart/FSharp.Compiler.Service that referenced this issue Jul 2, 2014
See fsharp/fsharp#50

The comments in FSharpBuild/Fsc.fs explain a bit more. It is realy hard
to work out how to make this perfectly consistent. Essentially, be
careful using resources in folders if you want your projects to be
portable across VisualStudio/MSBuild and mono/MonoDevelop/XBuild

We hit this bug in fsharp/fsharpbinding, but we've moved that to no
longer put resources in folders for now.
directhex pushed a commit to mono/linux-packaging-fsharp that referenced this issue Sep 17, 2014
See fsharp/fsharp#50

The comments in FSharpBuild/Fsc.fs explain a bit more. It is realy hard
to work out how to make this perfectly consistent. Essentially, be
careful using resources in folders if you want your projects to be
portable across VisualStudio/MSBuild and mono/MonoDevelop/XBuild

We hit this bug in fsharp/fsharpbinding, but we've moved that to no
longer put resources in folders for now.
enricosada pushed a commit to enricosada/fsharp that referenced this issue Jan 23, 2015
…ixes fsharp#50

closes fsharp#73

commit e127dfaa034ce8a515bb7aae57dc9c0d7e56a175
Author: Steffen Forkmann <steffen.forkmann@msu-solutions.de>
Date:   Wed Jan 21 10:52:10 2015 +0100

    fix typos in XmlDocumentation.fs and ast.fs

commit 6f9902997b42ceddeb8ff4db7f533000e5b23998
Author: Steffen Forkmann <steffen.forkmann@msu-solutions.de>
Date:   Wed Jan 21 12:17:58 2015 +0100

    Obsolete members are now also omitted in QuickInfo - references fsharp#50

commit ae547469cca7d50cde5feb6b4329e35e3f14d5c4
Author: Steffen Forkmann <steffen.forkmann@msu-solutions.de>
Date:   Wed Jan 21 12:17:16 2015 +0100

    Capturing broken QuickTip for obsolete methods in test - references fsharp#50

commit 1e38a8a8889a805880c30cdb05075704e5732206
Author: Steffen Forkmann <steffen.forkmann@msu-solutions.de>
Date:   Wed Jan 21 10:51:23 2015 +0100

    Members hidden from IntelliSense are now also omitted in QuickInfo - fixes fsharp#50

commit 5f27136d47c72ed2d9d502105ee5f65814e2c088
Author: Steffen Forkmann <steffen.forkmann@msu-solutions.de>
Date:   Sun Jan 18 10:49:41 2015 +0100

    Capturing broken QuickTips for hidden methods in test - references fsharp#50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant