.hep file is not loaded in WSL feature Please implement this in next version of rhapsody

Hi Team ,

Sorry for the inconvenience caused :

please find the below user provided information for your queries:1. What is the specific need for using WSL in this context?
The need for WSL is that the project is fetched (together with all needed build toolchains) and then build in Linux environment. The WSL approch provide same build environment for all developers and this approach is not unique for Visteon.Inside the project one of the component is a Rhapsody project. In order to update it developers have to manually copy it to Windows instead of open and using it directly from the project workspace in WSL.
Note there is no problem Rhapsody to generate the configuration to a WSL folder - the problem is only with loading the .hep file 2. wsl.localhost is a local Linux instance
->It was installed like this:
wsl --set-default-version 2
wsl --install ubuntu 3. The rhapsody project, the .hep file and java plugins are all part of the same project workspace and as such all inside the WSL itself.
The way it should work is this:
- developer fetch the project workspace in WSL
- maps the WSL folder to a drive and opens the Rhapsody project
- the java plugins specified by the .hep file are loaded; The .hep file is provided as a relative path...in the example shared to you: "../../ExternalChecks/Checks.hep"
- developer uses the java plugins for some automation; after Rhapsody model update is completed C++ code is generated in the WSL folder
- Now inside WSL linux console the project can be built (including the newly generated C++ code from Rhapsody What developers currenly have to do is after they fetch the project, the need to copy the rhapsody project to windows, open it from there, generate C++ files and then copy the generated files back to WSL and build the project
This is rather clumsy with several manual copy/paste steps 4. With "net use" the result is the same - the .hep file is not loaded.

Hi,

I hope you're doing well.

This is a final follow-up regarding the review request.
As we haven't received any feedback despite multiple reminders, we will proceed with closing the RFE.
If needed, we can reopen it or create a new one as required.

Regards,
Suneel...

Hi Puneeth,

Have you had a chance to receive the user's response?
I look forward to hearing from you.

Regards,
Suneel...

Hi SUNEEL ,

We are checking with user on the below requested information . Currently user is ooo will give you update once he is available.

Hi,

Have you had a chance to review the response?

Looking forward to hearing from you.

Regards,
Suneel...

Hi,

We have a few questions regarding this topic for your clarification:
What is the specific need for using WSL in this context?

Is wsl.localhost functioning as a network computer or as a local Linux instance?

What is the rationale for placing the .hep file in this particular location?

Have they considered using net use instead of subst?

Regards,
Suneel...