Open Tim-Maes opened 3 years ago
Managed to migrate the project, all VSIX code is now in a shared library, and a VS2022 targeting library which uses that shared dll has been added. Pull request here. Still need to test on older versions but if all goes well, I'll be packaging and releasing by the end of this week.
Edit - I take back those words as testing exposed issues
Managed to migrate the project, all VSIX code is now in a shared library, and a VS2022 targeting library which uses that shared dll has been added. Pull request here. Still need to test on older versions but if all goes well, I'll be packaging and releasing by the end of this week.
Those are some great news. My colleagues and me are looking forward to it. Thank you for your hard work.
it has been a long time since I mothballed my project, but just this week am looking to re-launch it and smack bang in the middle of it, I have some crucial T4 templates. Can't wait to see this new version, and am very grateful for the long term commitment to keep it up to date.
Currently experiencing 2 issues while updating this extension:
Currently WIP on this branch .
I keep you posted, help is also very welcome :)
Hey Tim,
are there any news about Visual Studio 2022 support?
Cheers, Founntain
Works have started again. https://github.com/Tim-Maes/T4Executer/pull/4 Still running into some issues. If we get them fixed, T4Executer will be shipped separately for VS2022 as it's own extension.
The solution is to replace DTE events with the new Community Toolkit events. I still run into issues doing that :/ -> https://github.com/ErikEJ/EFCorePowerTools/issues/1046
@Tim-Maes , any update on this VS2022 support?
Update: Managed to get it working now somehow :)
Please try downloading from the marketplace and validate if it works for you.
Is there any news about this feature?