Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

VS2015 extension is missing #9

Open
wldevries opened this issue Apr 5, 2016 · 3 comments
Open

VS2015 extension is missing #9

wldevries opened this issue Apr 5, 2016 · 3 comments

Comments

@wldevries
Copy link

Although it seems someone else has created a binary

http://blogs.msdn.com/b/maheshk/archive/2015/11/14/open-xml-package-editor-for-visual-studio-2015.aspx
@ghost
Copy link

ghost commented Nov 7, 2016 •
edited by ghost
Loading

Unfortunately it is no longer hosted at the location on that page. (The link http://blogs.msdn.com/b/maheshk/archive/2015/11/14/open-xml-package-editor-for-visual-studio-2015.aspx still works, but the link on that page to the binary no longer works.)

However, it was not much work to download the current version and tweak it to build for VS2015.

@filmico
Copy link

filmico commented Dec 30, 2016

Guys, as you've said the link with the compiled version for 2015 is down!

Here, you have a detailed steps on how to compile it on 2015.

  1. Open the OpenXMLEditor.sln with VS2015. It automatically get converted, saved and re-opened again.
    The migration report should indicates 0 errors.
    If it says that you need to download the SDK, go ahead download and install it.

  2. With the project open, I noticed a reference called Microsoft.VisualStudio.Shell.10.0 that was marked with a Triangle.

  3. Use Nugget and add vssdk.shell.10

  4. Right Click on the solution and perform Build...
    The vsix file should be located at \bin\Debug\OpenXMLEditor.vsix
    Close Visual studio and execute that file...

Kind regards to the developer for such and incredible tool!
cheers

bsivanov referenced this issue in bsivanov/Open-XML-Package-Editor-Power-Tool-for-Visual-Studio Jun 28, 2017
@bsivanov
Add support for Visual Studio 2017
2f45e68 
Upgrage the .vsix manifest to version 3.0, which is required for Visual Studio 2017 support. This drops support for Visual Studio 2010, but this is the recommended approach by Microsoft. If such support is needed, new extension with new Id should be provided.

Add some references as packages, so that the project could be build on machines where older versions of Visual Studio are not installed.

The source code is now only buildable using Visual Studio 2017, which is also limitation of the new VS extensions approach.

Fix issues #9 and OfficeDev#11.
@bsivanov
Copy link

Hello guys, I forked the extension with support for Visual Studio 2017/2015/2013/2012. It's published on Visual Studio Marketplace here: Open XML Package Editor for Modern Visual Studios.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wldevries @bsivanov @filmico