As for the other stuff — well 80683 is still open, to lets wait until that is actually fixed?
Yeah, probably expected. this used to be a file and its now a folder, and the old installer doesn’t know how to cope with that.
1 Like
I will do that now - staying on 2309, that still uses MSBuild until it is fixed.
I’ve just tried this and it works:
I’ve installed the latest build and replaced
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\RemObjects Software\Elements\RemObjects.Elements.Echoes.targets
C:\Program Files (x86)\MSBuild\RemObjects Software\Elements\RemObjects.Elements.Echoes.targets
with a copy of RemObjects.Elements.Echoes.Legacy.targets
1 Like
Yes, that is correct.
But I have several dll projects that are part of all my projects.
To be able to build a webservice, I have to set it to legacy. And all the dll’s in the same projects too.
But these dll’s are also part of other projects, and because I have to set them to legacy for a webservice, I have to set these other projects to legacy too, ending up in editing all my project files to legacy.
No, you haven’t understood me.
I didn’t edit the project files, but I replaced the file itself in
C:\Program Files (x86)\MSBuild\RemObjects Software\Elements
and
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild
So the compiler will still search for RemObjects.Elements.Echoes.targets, but the contents of that file will be the legacy targets.
I am going to try 
1 Like
YES !!!
It works !!!
Thank you very much!
back on 2313.
@mh I think I see progress in this. Looks like it compiles almost everything. I’m still testing.
Just two things:
-
Seems to be a problem when referencing the new Visual C# project structure. In this case I was trying to reference this one, so it can be tested easily:
https://github.com/stripe/stripe-dotnet -
When I tried to publish, EBuild says
Error () Build encountered more than 1000 errors or warnings. Further messages will be supressed.
(Yes maybe there are a few warnings right now…
) But the problem that message is not a warning, but an error, and it stops the publishing process.
I’m gonna try without so much warnings and see if it works.
Oops. Fixed.
can you elaborate?
ok, but…
but what is the problem you’re reporting? I don’t like looking at test cases and having to guess whether the behavior I’m seeing is the one thats ostensibly being reported or not.
Sorry,
Error () Project Reference '..\ClassLibrary2\ClassLibrary2.csproj' could not be resolved for target 'Echoes' (Echoes .NET anycpu). ReferenceVC C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\RemObjects Software\Elements\RemObjects.Elements.Echoes.targets 53
Thanks, logged as bugs://80800
Jose,
your Hint path is wrong:
<ProjectReference Include="..\ClassLibrary1\ClassLibrary1.csproj">
<Name>ClassLibrary1</Name>
<Project>{4472ed52-38a1-405c-89d8-7c7770ff19ae}</Project>
<Private>True</Private>
<HintPath>..\ClassLibrary1\bin\Debug\ClassLibrary1.dll</HintPath>
</ProjectReference>
<ProjectReference Include="..\ClassLibrary2\ClassLibrary2.csproj">
<Name>ClassLibrary2</Name>
<Project>{eeb01a44-fc7b-480a-a965-43916362db58}</Project>
<Private>True</Private>
<HintPath>..\ClassLibrary2\bin\Debug\netstandard2.0</HintPath>
</ProjectReference>
this
<HintPath>..\ClassLibrary2\bin\Debug\netstandard2.0</HintPath>
should be
<HintPath>..\ClassLibrary2\bin\Debug\netstandard2.0\ClassLibrary2.dll</HintPath>
bugs://80800 got closed with status testcaseerr.
Sorry, it seems I missed the notification for this.
That HintPath is not set by me, manually. I’ve just added the reference in VS with the add reference dialog.
They are all empty projects, just as VS creates them, nothing special.
I’ve just changed the HintPath and it builds, but if I remove the project references and re-add then in VS, the HintPath is wrong again, so it doesn’t build. So there is the bug then?
bugs://80683 got closed with status fixed.