I am creating a project in VS2015. template i have choose is blank Universal app.
An error occurred trying to load the page.
Property accessor 'TargetDescriptions' on object
'Microsoft.VisualStudio.ProjectFlavoring.Automation.Project.CommonProjectExtender'
threw the following exception:'Value cannot be null. Parameter name:
targets'.
I get issues accessing some projects properties due to addins I've added to my VS (GhostDoc): can you try to disable all your addins to check of that work ?
I reinsatlled the nuget package manger: https://visualstudiogallery.msdn.microsoft.com/5d345edc-2e2d-4a9c-b73b-d53956dc458d
I restart the visual studio
and it works fine for me.
Related
I have a VSTO for Excel project with a custom ribbon tab. The solution builds without errors. I can run the solution. It launches Excel and displays the custom ribbon tab and task pane without any issue.
When I try to open the designer for the custom ribbon tab in Visual Studio 2019, I get the following error:
Could not find type 'Microsoft.Office.Tools.Ribbon.RibbonTab'. Please
make sure the assembly that contains this type is referenced. If this
type is a part of a development project, make sure that the project
has been successfully built using the settings for your current
platform or Any CPU.
The solution builds and runs without any issues.
When I expand the error info, There is no stack trace or error line information available for this error.
The build settings are set to 'Any CPU'.
The assemblies that contain 'Microsoft.Office.Tools.Ribbon.RibbonTab' are included in the project references. These are Microsoft.Office.Tools.Common and Microsoft.Office.Tools.Common.v4.0.Utilities.
I have tried to Clean, Rebuild, and Restart Visual Studio 2019. This had no effect.
I could not find anything definitive when I Check Windows Forms Design-Time error list.
Would anyone know how to address this issue so that I can open the custom ribbon in the designer?
Is VSTO still supported by Microsoft? All documentation appears to be several years old.
This is a Visual Studio issue, not a C#/Build/DLL linkage issue.
Make sure your Visual Studio setup (do the Modify in the installer (#1) if already installed) has these two components checked:
Is VSTO still supported by Microsoft?
They are moving to an online office365 addin (my words) type VSTO. As to new features, not recently. One can still put in a Visual Studio support ticket if you have the right subscription.
I have never had any issues with ribbons, but sometimes the winforms res files in designer do not show and I use the JetBrains Rider editor to view those controls when VS fails.
I am trying to overcome this error in Designer Mode of any ASPX page,
for example, CS203100 out-of-box:
I am not sure when the error began, and not sure if this could be related to any recent Windows Update. I am working with AcumaticaERP version 18.1.102.0048 under VS2015 on Windows 10 Enterprise. The error occurs under TargetFramework 4.5.2 and also after updating to 4.7.1. Any help please would be great, thanks!
We ran into the same issue with a colleague and it turns out that Visual Studio was not running with administrative privileges. It looks like PXLicenseObserver tries to create a log file on initialization and it fails when Visual Studio is not running in Administrator mode.
Hi I am using Worklight to develop application for Windows Phone 8. The application was working fine, however when I applied the Fix Patch for Worklight the Windows Phone Console started to give me below error :
An exception of type 'System.NotSupportedException' occurred in Microsoft.Phone.ni.dll and wasn't handled before a managed/native boundary
The other error is
Error:"Unable to get property 'content' of undefined or null reference file:x-wmapp0:/www/skinLoader.html Line:1"
Any one has any idea why these two errors started coming all of sudden?
Moreover, where can I change Worklight specific properties in Visual studio?
Moreover, where can I change Worklight specific properties in Visual
studio?
There are no "Worklight specific properties" in Visual Studio.
Once you build the Worklight project in Eclipse and open the result (in your case, the generated Windows Phone 8 project) in Visual Studio, that's it - it is a Windows Phone 8 project.
Error:"Unable to get property 'content' of undefined or null reference
file:x-wmapp0:/www/skinLoader.html Line:1"
Try to:
Delete the native folder in Eclipse from the your-project\apps\your-app\windowsphone8 folder
Re-build and deploy the application
Re-open it in Visual Studio
As for the SystemNotSupportedException message, this can be safely ignored.
I've just installed VS2012 Ultimate side by side with VS2010 and it seems the standard templates are broken. I cannot add a class nor a console application.
File > New > File dialog contains the "Visual C# Class" template
but Right Click Project > Add > Class dialog does not contain the "Visual C# Class" template
Also File > New Project only contains MVC4 and not things like Console Application even if I change framework version and left filter.
EDIT: This only occurs after installing update 1. We have tried reinstalling, repairing, deleting the templates cache and reinstalling templates. We're considering working without update 1 at the moment, but there doesn't seem to be a way to uninstall just the update.
Corrupted ISO supplied, tried another from msdn and all fine now.
Steps to reproduce:
Create a new xamarin forms app
Build iOS => Ensure it builds successfully
Add the iOS component for Firebase Cloud Messaging for iOS from the component store
Clean, Rebuild => Notice you get object reference error while compiling the iOS project
Here is the error from output window:
"src\RepeatReturns\packages\Xamarin.Build.Download.0.2.2\build\Xamarin.Build.Download.targets(25,3): error : Object reference not set to an instance of an object."
Any idea how can we fix this?
Thanks
UPDATE:
If it helps, I have the linker option for iOS set to "link SDK assemblies only".
If you are using Visual Studio 2017 RC, then I suggest that you stuck with Visual Studio 2015 for the moment, I had the same issue, and I didn't find any solution. So I reinstalled VS 2015, and everything is working now.