-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please release a new version #57
Comments
good job! We need it, thanks! |
Yes please. At least to fix the incompatibilty with Visual Studio 2022 >=17.2. |
New build created under actions. Will try to release this version via VS portal. |
Thank you Bert! Now I can see the new artifact under Actions, but only for 2017-2019. It seems the build failed building for vs2022. "C:\Users\runneradmin.nuget\packages\microsoft.vssdk.buildtools\17.0.5232\tools\VSSDK\Microsoft.VsSDK.targets(829,5): error MSB4018: [D:\a\AnkhSVN\AnkhSVN\build\src\Ankh.Package\Ankh.Package.csproj] |
Looks like build 2019 failed, just after the 2017-2019 one, and never got to the 2022 one. I really appreciate all your work on this. Maybe is some way to just run 2022. Or maybe it's the dependency downloads at all. I'm trying to build it also, but im not sure how to deal with the QQ turtles, and not having 3.5 installed. |
any news on the build for VS2022? Thanks a lot! |
Oh yes, please create a new vsix for VS2022. Microsoft urged me to switch from 2019 to 2022, and now I am heavily missing my AnkhSVN plugin... |
I built the attached from source on my VS2022 install and was able to install the VSIX once built. Hope this works for you and can hold people over until there is a new release! |
@ARMoir First impression looks good. Thank you so much!!! |
I forked the repo https://github.com/ARMoir/AnkhSVN and I am going to be making some small updates, hopefully my pull request gets approved. |
Thanks - will this install happily over the official 2019 build? |
I believe it should if you use the Ankh-VSIX-2017-2019 Artifact, but please let me know what you find. |
That installed ok and seems to be operating fine, but I do have two entries for AnkhSVN in extension manager now. The old one is ver 2.9.87, the new install is 2.9.3 I uninstalled the old version (2.9.87) and all seems ok. |
Update - I misunderstood your directions, I was using 2019 in VS2022 and installed your 2022 over the top of it, I guess that's why I had two versions in Extension manager. Regardless, it works fine, thanks. |
@Blackpaw No problem! Yeah the build numbers reset on the github actions when I forked the repo, so that's why it went from 87 to 3. I made a few more updates and I am only building for 2022 now, as that is what I am using, glad if it helps! |
Where can I get the new version? VS2022 |
@nikeruga |
Thank you, early days but your fork seems to resolve the instability issues I was getting on main. |
Here's a 2022 build using more direct means. It's from my AddOn Studio releases basically, which now having to build AnkhSVN also. The reason couldn't include the other one is because it effectively sets the minimum VS version at 17.5. This is built in a more basic way, that's more in-line with the setup for other VS components. |
Updated link in case the github redirect goes away. Moved to the same umbrella as AddOn Studio. https://github.com/FallenWorlds/AnkhSVN Another, more final release today |
@rhuijben Could you please create a new release for VS2022? |
The latest available build from Github Actions for VS 2022 has expired. The current released version lacks a few important bug fixes. There is currently no recent build available for VS 2022.
The text was updated successfully, but these errors were encountered: