Project output path not respected

More
2 months 2 days ago #1 by Kromi
Project output path not respected was created by Kromi
Hi,

the executable project of our solution has set the output path to a non-standard value, but this setting is ignored and all files are created in bin/$(Configuration).

Is this a known issue with VS 2017/X# 2.0.0.5?

Regards,
Mathias

Please Log in or Create an account to join the conversation.

More
2 months 2 days ago #2 by robert
Replied by robert on topic Project output path not respected
Mathias,
Can you send me the xsproj file ?

Robert

XSharp Development Team
The Netherlands
This email address is being protected from spambots. You need JavaScript enabled to view it.

Please Log in or Create an account to join the conversation.

More
2 months 2 days ago #3 by Kromi
Replied by Kromi on topic Project output path not respected
Sure, here it is. I have tried with the original setting from the Vulcan project (using the SolutionDir variable) and with an absolute path, both with the same result.

One additional minor thing: Sometimes PropertyGroup tags containing build configuration info are added at the end of the xsproj file instead of the top of the file, so the various configurations are spread over the file. You can see this in the file I have attached. Is there a chance that this will be changed sometime in the future?
I know that these files are not actually meant to be read by humans but we have to edit project files quite often in order to fix assembly references.

Mathias
Attachments:

Please Log in or Create an account to join the conversation.

More
2 months 2 days ago #4 by robert
Replied by robert on topic Project output path not respected
Mathias,

You are seeing multiple property groups because you have multiple (2) platforms defined as well as configurations (2). There is a property group for each combination, so 4 in total.

Your project file contains entries for Platform AnyCPU and x86.
And the Configurations Debug and Release.
I see the following values:
Debug|AnyCPU $(SolutionDir)..\..\client\
Release|AnyCPU $(Configuration)
Debug|x86 C:\Source\TrunkX\Client\
Release|x86 $(Configuration)\

At the end of the project file there are also property groups for the pre and post build events.
I would merge the values from the AnyCpu and x86 property groups into the AnyCpu propertygroup. Duplicate entries in a property group are not a problem. The last one will be used.
Once you edit the project properties inside VS then our project system will remove duplicate entries in the same propertygroup.

Robert

XSharp Development Team
The Netherlands
This email address is being protected from spambots. You need JavaScript enabled to view it.

Please Log in or Create an account to join the conversation.

More
2 months 2 days ago #5 by Kromi
Replied by Kromi on topic Project output path not respected
Robert,

Just to clarify, I have not added any build configurations into the project file with a text editor, if that is what you assume. The file as you see it is how Visual Studio saved it when I last changed something via the projects properties page.
Incase this is relevant: The project file was originally created by the XPorter tool from a vnproj file.

What I don't understand is this:
In VS configuration/platform for the solution is set to Debug/x86. With the Configuration Manager I have checked that all projects are set to the same. One of these projects is the one I have attached the xsproj file from. If I open the properties page of that project I see the output path is set to "C:\Source\TrunkX\Client\", but when I build the solution and check that directory I don't find the new files. Instead, they are at "bin\Debug", a path that appears nowhere in the project file. Am I still missing something here?

Regarding the order of tags in the project file:
I know that in the project file there is a PropertiesGroup tag for each build configuration and platform combination I have set up, what I don't like is that some of these tags are at the beginning of the file and others are at the bottom. (As I said, this is a minor thing, not a real problem.)

Mathias

Please Log in or Create an account to join the conversation.

More
2 months 2 days ago #6 by robert
Replied by robert on topic Project output path not respected
Mathias,

Someone must have edited the project file. Either by hand or by adding a platform inside Visual Studion.
Vulcan does not have the platform only the configuration. When transporting the project file with our exporter then only a AnyCPU platform is added.
Only when you have more than one platform then you will see that the propertiesgroup is at the end of the file.


Robert

XSharp Development Team
The Netherlands
This email address is being protected from spambots. You need JavaScript enabled to view it.

Please Log in or Create an account to join the conversation.

More
2 months 2 days ago #7 by Kromi
Replied by Kromi on topic Project output path not respected
Robert,

ok, then I misunderstood you, I added the x86 configuration to all X# projects. But do you have an idea regarding the actual problem which is that the output directory setting is ignored?

Mathias

Please Log in or Create an account to join the conversation.

More
2 months 2 days ago #8 by robert
Replied by robert on topic Project output path not respected
Check 'Build - Configuration manager' in VS.
This shows which project platforms are linked to which solution platforms. My guess is that there is a mixup. Maybe a solution platform x86 is linked to a project platform anycpu ?
When not then I need to see more. Then I also need the solution file.
Robert

XSharp Development Team
The Netherlands
This email address is being protected from spambots. You need JavaScript enabled to view it.

Please Log in or Create an account to join the conversation.

More
2 months 1 day ago #9 by Kromi
Replied by Kromi on topic Project output path not respected
Robert,

I double-checked with the Configuration Manager, all projects are on Debug/x86. I've attached the solution file, hope you find something there.

Mathias
Attachments:

Please Log in or Create an account to join the conversation.