Closed Herdo closed 7 years ago
Do you intend to update this for Visual Studio 2017?
@nishantkagrawal Sure. I'll do as soon as I have the time for it :) It might happen before the release, but due to local events, it might happen in the week after the 7th March.
@nishantkagrawal The issue is currently blocked. Visual Studio 2017 doesn't allow the migration of the primary project from 2015 to 2017. The error is described here: https://developercommunity.visualstudio.com/content/problem/27059/unable-to-migrate-preview-core-projects.html
@nishantkagrawal The development is comming to an end. I'll keep the style of the VS 2015 start page as it is providing more space than the VS 2017 start page. I'll be writing some tests the next days, do some minor adjustments and probably release soon :)
During final deployment testing, I found out that the new VSIX 3.0 format is only compatible with VS 2015 and VS 2017 (maybe 2012/3) as well. However, not with 2010 any more.
So I'll either drop support for old VS versions, or supply multiple packages... Thoughts?
2010 and 2017 are IDEs with vast time span! I think it should be ok for you to drop support for old versions, given that the one who want to use it with 2010 can use the older version of IDE. Why would someone use 2010 and 2017 together! I use 2015 and 2017 together. People might be using 2013/2017 together but not 2010/2017.
This VSIX is a preview - my local installation is corrupted: Getting the error: "FindNotFoundException - (my installation directory)\VS15Preview not found".
@nishantkagrawal Feel free to download the ZIP, rename to VSIX and hit it. If you have an idea about how to fix that annoying error of mine, feel free to contact me.
I'll have to check this at my workplace. SolutionStartPage.zip
Additional preview. SolutionStartPage.zip
@Herdo the current preview is not showing up in the Customize Start Page drop down. VS 2017 Enterprise, Windows 10 (10.0.14393)
@martosource Thanks for the report, I found the same issue at work but couldn't validate it on my dev machine. I'll try to find a solution for that issue.
Looks like migrating the vsixmanifest removed the "start page" definition. I'm going to validate this tomorrow.
I needed to change the vsixmanifest Content tag to
<Assets>
<Asset Type="Microsoft.VisualStudio.VsPackage" Path="StartPage.pkgdef" />
<Asset Type="StartPage" Path="StartPage.xaml" />
</Assets>
It is now working, but it is not pickup the dark theme setting.
Thanks @martosource for the help here! I included that fix in the current vsixmanifest - tested - works fine. I'll put up the release later today with 2 known issues.
Version 3.0.0 released.
Known issues:
FYI: @nishantkagrawal @martosource
Visual Studio 2017 will require a new version of the extension. As soon as the SDK for Visual Studio 2017 is available, the development can begin.