I developed a Project Template for/with Visual Studio 2017. This extension does work as expected when I debug it.
I now try to add it in Visual Studio Gallery but the website does not validate my extension. I just get a generic error message : "Invalid model file in VSIX" (maybe poorly translated from French)
Is there any way to prevalidate my VSIX with a tool or get more information about what is wrong with my extension?
Thanks
It seems that VS Gallery does not support VSIX that targets explicitly framework 4.6.2
Targeting 4.6 only did the trick
Related
I am trying to update my published Visual Studio extension to the 2022 version, this one
The problem is: I keep getting (when attempting to update on the marketplace).
The extension is incompatible with the targeted version of Visual
Studio. More info at https://aka.ms/ExtensionSdkErrors
Locally, the extension installs and runs fine (on 2022 as well), this version that can be downloaded from the "GitHub releases", and there are no blocking messages when building it as well from the analyzers.
The link in the error message says that the extension should be using the latest version of the VisualStudio.Sdk (version 17). The thing is, it does!
Any suggestion what I could look at to make the submission succeed?
Extension has two bundled child project templates inside, and one template wizard (in addition to the SDK it has a reference to Microsoft.VisualStudio.TeamplateInterface v.17), because SDK does not seem to have this package bundled.
Full source code:
https://github.com/nbelyh/VisioPanelAddinVSTO/tree/vs2022
Many interop assemblies were embeddable prior to Visual Studio 2022. Beginning in Visual Studio 2022, embedding is no longer required or supported.
try removing the references from the project file https://github.com/nbelyh/VisioPanelAddinVSTO/blob/master/Wizard/PanelAddinWizard.csproj
envdte
EnvDTE80
Microsoft.VisualStudio.OLE.Interop
Microsoft.VisualStudio.Shell.Interop
and use the Microsoft.VisualStudio.Interop
You can refer following list:
https://learn.microsoft.com/en-us/visualstudio/extensibility/migration/migrated-assemblies?view=vs-2022
For more details:
https://learn.microsoft.com/en-us/visualstudio/extensibility/migration/update-visual-studio-extension?view=vs-2022
When I try to install Prism in my Xamarin application in visual studio I get this error
"[nuget.orgUnable to load the service index for source http://prism.azureedge.net/main.mrep. The content at 'http://prism.azureedge.net/main.mrep' is not a valid JSON object. Unexpected charater encountered while parsing value: <.Path ", line 0, position0.]"
I can't say I'm entirely sure what you're doing, but let me try to clarify some things for you.
The URL http://prism.azureedge.net/main.mrep is ONLY meant to be added as an Extensions Repository Source for Visual Studio Mac. It has nothing to do with NuGet and is not compatible with any other version of Visual Studio. That feed provides the Visual Studio Mac Extension to provide the Prism Project & Item Templates as well as several code snippets.
If you are looking for the Prism CI Feed to take advantage of the latest Prism build you need to add https://www.myget.org/F/prism/api/v3/index.json as a NuGet Package Source.
We have large project that used .NET Framework for showing forms/windows. Recently I decided to deprecate CLR dependency and move to Qt.
While learning Qt, we've migrated from Visual studio 2013 to 2015 and then I noticed that there is no qt support for MSVC 14 version which vs2015 use.
Additionally, Qt vs addin was not working jn visual studio express/community edition we use. Is there any chance for me to use Qt and qt addin in our projects?
Searching web did not help, and it looks like no one use Qt with latest Visual Studio?
Building
You can use Qt in Visual Studio 2015 without any problems. As already stated in the comments, you have to build it from source but Qt is pretty straightforward to build. You can download the current (5.5) sources here and then follow this step by step example on building it.
I would also suggest reading more about the configure options, this might save you a lot of time. It might possibly save you some external dependencies as well if you skip components you do not need. My configuration for instance contains -skip qtwebkit -skip qtwebchannel so I do not need ruby or python.
I could totally omit step 3 from the link. Just be sure to open the Visual Studio Command Prompt (32/64 is important here) for configure and nmake.
Usage
For Visual Studio 2015, the Qt Add-In is not available anymore. But there is an Extension (Tools > Extensions & Updates) called Qt5Package or QtPackage which has the same functionality. After installing it, you have the Qt entry on your main toolbar where you have to specify a version and the path to the directory where you built it. This version will also be associated with the current project via the same menu.
If you load an existing project, you also have to convert it so the whole Qt functionality is used automatically. You can do this by opening the solution and right click on it; there should be an entry for the conversion to a QtAddin generated project.
I am using Qt 5.5 on Visual Studio 2015 with an old project and it is working without any issues.
As of now, you can just download Qt for Visual Studio 2015. Here.
Qt have finally added support for Visual Studio 2013 and 2015 although it's only in beta right now. See QTVSADDINBUG-404 for progress and read the blog post From Visual Studio Add-In To Qt VS Tools (Beta).
The Qt Windows could be added to the current project by copying all relating necessary files from the Qt stand-alone project to the current project. Specifically, the following steps must be conducted carefully.
Create an example project of Qt inside a Visual C++ project by using a Qt Plugin Program. The windows must be designed inside this project carefully before adding to the existing project.
Inside the existing project, add carefully the file heloqt.cpp, helloqt.h, ui_helloqt.h, qrc_helloqt.cpp, moc_helloqt.cpp in case of the Qt Project having the name of helloqt.
Add some configurations of Additional include directories and Additional library directories and Additional Dependencies into the existing project.
Compile and add some required *.dll files for running the program.
I have to do that because I want to use a graphic user interface in my big project, and this project is too big to be added into the Qt project inside the Visual C++ Studio.
I am developing a Visual Basic project in Visual Studio 2010 that uses ArcObjects. (I have ArcGIS 10.3 for Desktop.) I am getting the error "'RuntimeManager' is not declared. It may be inaccessible due to its protection level." A previous answer, Esri ArcObjects--Esri.ArcGIS.Version assembly, recommended adding a reference to Esri.ArcGIS.Version by clicking on Project, Add Reference, selecting it under .NET and clicking OK. I have tried to do this, but it's not under .NET. What can I do to make it available?
You should be able to find it if you use the Browse option.
The ESRI.ArcGIS.Version.dll file should be under your DeveloperKit installation folder. For me it is:
C:\Program Files (x86)\ArcGIS\DeveloperKit10.2\DotNet
I am trying to convert a SharePoint 2010 solution (custom web parts, content types, lists, event receivers, etc.) developed in Visual Studio 2010 to SharePoint 2013 and Visual Studio 2012. When I open the project in VS 2012, it converts a couple of the project files but won't compile because of reference issues.
I copied the DLLs (mostly Microsoft.SharePoint..., although I needed to copy the Microsoft.Office.SecureStoreService.dll too) that were causing issues from my 2010 server to the 2013 server and fixed the references. However, the Microsoft.Office.SecureStoreService.dll still gives me compiler errors claiming "Error 203 The type or namespace name 'Office' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)" when visual studio has no problem with the namespace and finds the SecureStoreProvider class inside it just fine.
I've also tried to change the target framework from 3.5 to 4 and only see "Install other frameworks..." in the target framework dropdown.
I'm sure that others have dealt with this, but have been unsuccessful in framing the right google search query. I'm relatively new to SharePoint in general and any help would be appreciated.
thanks,
Mike
I was able to get my solution upgraded from a 2010 project to 2013 using the following. Note that this will update your solution to use the new 2013 API. It is possible to update just the project file but still run in 2010 mode.
First edit your .csproj file (for c#).
Modify the target framework to this:
<TargetFrameworkVersion>v4.5</TargetFrameworkVersion>
Add this a node for the office version, I put mine directly below the TargetFrameworkVersion tag
<TargetOfficeVersion>15.0</TargetOfficeVersion>
Update references
Reload the project and update your referenced assemblies. If you haven't specified a specific version they should already be referencing the v15 (SharePoint 2013) assemblies.
Do a find replace for 14.0.0.0 to 15.0.0.0. This updates any references on your pages, layouts, and master pages to the v15 assemblies.
Change calls
Change any calls to SPUtility.GetGenericSetupPath() to SPUtility.GetVersionedGenericSetupPath()
Check each file to do a check for any hive references. You'll need to add a /15/ to these. EG: _layouts/ to _layouts/15/
Open the package "folder" in visual studio then update the properties for that package to use version 15.
Clean up
Finally do a compile clean up any missed items. Deploy your solution and make sure to test thoroughly.