Power-Maverick / DataverseDevTools-VSCode

The all-in-one tool to develop code for Dataverse/Dynamics 365. Helps you connect to a Dataverse environment, generate TypeScript definitions for entities, create a different type of Dataverse-specific projects, and much more.
https://marketplace.visualstudio.com/items?itemName=danish-naglekar.dataverse-devtools
MIT License
58 stars 15 forks source link

[Bug]: linker file is not an xml according to standard because of version attribute #171

Closed David-Cadmart closed 2 weeks ago

David-Cadmart commented 3 months ago

What happened?

I created a PowerShell script that uses the xml generated in the dvdt.linker.xml file to automate some actions. When I try to load the file as an xml I get an error. The issue is that the file has the version set like version="1", but the standard says that the version must be version="1.0". I can edit the file and make the script work, but when a new link is created, the file is regenerated, and I have to change it again.

Can the xml be updated to have the version like the standard?

Thanks

What version of the tool are you using?

v2.2.0

What version of Visual Studio Code are you running?

1.92.1

Any relevant session id from VSCode?

No

Relevant log output

No response

power-maverick-bot[bot] commented 3 months ago

Thanks for opening your first issue here! Please make sure you have given us as much context as possible. One of the repo maintainer will respond as soon as possible.

Power-Maverick commented 3 months ago

I am using fast xml parser to parse the file into xml. I'll have to check with that package if there is a config missing or if it's an issue with the package.

David-Cadmart commented 3 months ago

I don't know if it is relevant, but the linker file in the templates section has the correct value set for the version. I don't know if this file was generated with the same package, but just pointing it in case it helps. The file is the one in resources/templates/dvdt.linker.xml.

github-actions[bot] commented 2 months ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] commented 2 months ago

This issue was closed because it has been stalled for 5 days with no activity.

David-Cadmart commented 2 months ago

Can this be reopened? It is still not solved.

Power-Maverick commented 2 weeks ago

This should be resolved now