I had developed a VSTO module to Outlook using VB.NET and VS2017-Community.
At the first installation, it asked for an user authorization to install, showing the Product name and the Vendor/Manufacturer data, based on the ClickOnce compilation (I guess).
Everything rans ok...
But now I uninstalled completely this AddIn and, when I call the SETUP again (due to a newer version), the Outlook does not show this window anymore - the Ribbon is updated automatically, my custom ribbon appears, etc.
In other words: my new version is installed into Outlook seemless and runs perfectly; except for the fact of the VSTO window does not appear anymore during the Outlook load (which would be like I saw before at the 1.0.0 version of my software).
I would like to see a CLEAN installation, I mean, exactly what a user which had never installed my software would see.
Some data to enlight the problem:
1- I'm using MSI installation and uninstall. Everything runs 100%.
2- The uninstall clears all the registry keys and the application folder.
3- I saw %User%/AppData/Local/Apps/2.0 folder and, also, there are no references to my project.
4- I open REGEDIT and check the following keys. All of them are cleared (no references to my AddIn):
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\Resiliency\AddinList
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\1x.0\Outlook\Resiliency\DisabledItems
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\1x.0\Outlook\Resiliency\CrashingAddinList
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\1x.0\Outlook\Resiliency\DoNotDisableAddinList
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\1x.0\Outlook\Resiliency\NotificationReminderAddinData
(there are no Local_Machine key created here, my Office is 32-bit not running as Admin/Local_Machine).
So, how can I make a clean installation like I saw before?
I appreciate any help.
I found the solution!
We must clean the references also in:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\1x.0\Outlook\AddInLoadTimes
HKEY_CURRENT_USER\SOFTWARE\Microsoft\VSTO\SolutionMetadata
HKEY_CURRENT_USER\SOFTWARE\Microsoft\VSTO\Security\Inclusion (keys and subkeys)
That's it! :)
I installed Visual Studio Code 1.1 with the C/C++ extension,
opened my C++ project and tried to use "Go to definition" in vain.
The "Go to definition" is not working at all.
Example, go to definition of a class member:
int i = m_myVar;
(I opened a simpler project with one file and it was working for this one)
In the end, what I want is good indexation of my big project, is there a way to install Intellisense?
I had a the same issue: F12 and Ctrl + Click and Right Click "Go To Definition" wasn't working.
The fix for me was:
Go to Extensions
Click "Disable All Installed Extensions"
Close and Reopen VS Code
Back to Extensions and "Enable All Extensions"
Essentially enable/disable all extensions fixed the issue.
I recently came across this same issue and after trying all of the suggested solutions I could find with no success, I found this article:
https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc
Basically my project grew too large and VS code was no longer able to track all files, which messed up the "go to definition" functionality.
After following the steps on the link to increase the maximum number of files to be tracked, the issue was resolved.
The correction is pretty simple (tested on Ubuntu 18.04):
Add this line:
fs.inotify.max_user_watches=524288
to the end of the file /etc/sysctl.conf
After saving, run the following command:
sudo sysctl -p
Hopefully this will be useful to someone else, this has been bothering me for the last few days.
I had a similar problem except with Python and google searches for solutions kept bringing me back to this post so I figured I'd post my solution here in the hopes that it might help other people.
I was working on a remote cluster through VScode Remote and was getting similar errors to the original question(all 'go to ___' functionality was unavailable and was even getting a 'too large to track' error) and I thought I had to increase the number of watches, which didn't end up helping.
All I needed to do was install a python interpreter on the remote VScode server. This fixed my problem.
I believe vscode 1.1 (well, 1.1.1 actually) + the C++ extension (cpptools) is as much Intellisense as we can get for now.
You should load your big project with the "open folder" function to make vscode know about the other files.
https://blogs.msdn.microsoft.com/vcblog/2016/03/31/cc-extension-for-visual-studio-code/ warns about letting the indexing finish first (red icon in lower right corner during indexing) and mentions the current limitations on the source code parsing.
It wasn't working on my laptop as well after installing a few VSCode extensions. I decided to close and re-open VSCode with administrator permission and suddenly it sorted out.
I have been trying to fix this for a long time. In the end, what worked for me was simply reinstalling VSCode, then installing the latest C/C++ extension (v0.18.1). Then, in your .vscode/c_cpp_properties.json file, under includePath, add your include folder which has all your header files.
I tried the methods mentioned in this thread none of them seemed to work for me. A simple solution that worked for me is that I closed the current workspace and created a new workspace, added the folders which I required(same as the old workspace), and saved the new workspace. Waited for a couple of minutes to index and IntelliSense is able to find definitions now.
I am using VSCode 1.52.1 on Ubuntu 20.04.
In my case, for whatever reason,c_cpp_properties.json has become set to Disabled in ~/.config/Code/User/settings.json.
Manually changing it to Enabled solved the problem.
Fixed mine by UNCHECKING C_Cpp > Default > Limit Symbols To Included Headers
Your mileage may vary. Good luck!
Have you saved your workspace? Or did you just open a folder with File->Open Folder? This question already has many answers, but none of them address this case, which was my issue.
The question is not specific enough for me to know if you are having the exact same symptoms as my case.
If:
You have not saved your workspace. vscode doesn't say "(workspace)" at the top of the window.
None of the goto functions are working, but instead report: "No ___ found for ____"
The tag parser database icon in the bottom right is always there but only reports "Parsing open files", rather than telling you how many files have been parsed.
Then:
Try saving your workspace.
If you have multiple versions of a language on your PC, specify the exact language you are using in the VScode(in my case, I am using Python, so I must specify the version to the python Interpreter in VS Code)
If you could not do it whatsoever, then uninstall all the other versions that you don't use and then if you go to VS Code, it will ask the version to be used, and you would have only one version, so when you select the version, the "Go To Definition" will be activated.
I was having a similar issue with java on Ubuntu 20.04 using OpenJDK version 11 (openjdk-11-jdk in apt). At first I didn't have the JRE installed, so I installed it and it still didn't work.
Afterwards, I went to the CTRL + SHIFT + P menu and then to Java: Configure Java Runtime, there I saw in the Java Tooling Runtime tab that /usr/lib/jvm/java-11-openjdk-amd64 was selected, changed it to /usr/lib/jvm/java-1.11.0-openjdk-amd64 just to see if it would work, and after a restart it did. I'm not sure why this is, but I hope it may help somone else.
For python ensure your code analysis settings are correct. In my case the languageServer was accidentally set to 'None'. Reverting it to 'default' or 'pylance' did the trick.
Just to inform if none of above works then
In my case i was using Kite extension in my VS code, I just disabled it and it worked. I think kite extension is blocking this feature.
OS: Linux Ubuntu 22.04
if you encountered with following error:
"The .NET Core SDK cannot be located. .NET Core debugging will not be enabled. Make sure the .NET Core SDK is installed and is on the path."
Normally Vscode remains unable to locate .Net sdk. need to set path manually.
sudo ln -s /snap/dotnet-sdk/current/dotnet /usr/local/bin/dotnet
restart omnisharp & restart vscode
No need to do anything. Just close and re-open. It will work.
I also faced similar problem. In my mac os cmnd + 'click' is used to 'go to definition' then it suddenly stoped working. If that is the case then please follow these steps:
restart vs code
restart pc
uninstall all extensions and reinstall again followed by a pc restart.
I had a similar issue with the extension C/C++ installed. I solved it by downloading an older version of the extension and upgrading to the last version. Somehow it solved the problem...
I'm trying to install iCloud on my Windows XP Pro (SP3) PC. Officially it's supported only for Vista and later, but this hack is widely claimed to work:
Open iCloudSetup.exe file and unzip its files including
Navigate to and open the iCloud.msi with Orca.
In the left table select LaunchCondition. Then change in the right table “VersionNT> = 600” to “VersionNT> = 200” and Save.
Run modified iCloud.msi and install.
Run iCloud Control Panel, located in the Windows Control Panel, and set up as you want.
I tried that promising solution in vain. It seemed to successfully install iCloud, but whenever I try to run it I get
this obscure error
After much fruitless searching I've not found out how to proceed from there and would appreciate advice please.
That trick worked with only the firs versions of iCloud Panel, the v1.0.
For the v2.1 doing the trick the installer ran ok, but when trying to run the iCloud Panel it showed the error you're refering to.
I had some computers running with that older version without any problem.
Try downloading the v1.0 version here:
http://icloud-control-panel-for-windows.uptodown.com/descargar/22412
If you want to try the trick with the v2.1 you have the installer here:
http://icloud-control-panel-for-windows.uptodown.com/
Remember you need to extract the MSI from the exe to do the trick. After running the exe check the %TEMP% folder to get the MSI file.
I have a Glass GDK app (open-source on Github) that works fine on XE12.
I got the XE16 update yesterday, and now when I run gradlew installDebug to deploy to Glass, I get the message:
:onebusaway-android:installDebug
pkg: /data/local/tmp/onebusaway-android-debug-unaligned.apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Here are the changes I've made to update to XE16:
I've changed my compileSdkVersion to "Google Inc.:Glass Development Kit Preview:19"
I've updated the gdk.jar in the /libs folder to the file from <android-sdk>/add-ons/addon-google_gdk-google-19/libs
Added <uses-permission android:name="com.google.android.glass.permission.DEVELOPMENT"/> to manifest for pre-production voice commands
(I actually made these changes prior to receiving the XE16 update myself, based on reports of it failing on XE16 from others - so I can confirm that with the above changes the app still works fine on XE12).
I'm using this third-party progress bar library, but from what I can tell from the release notes nothing has changed with the GestureDetector or Gesture Glass classes, which are the only Glass-specific classes it relies on.
My Glassware is an immersive Activity, so I'm not relying on TimelineManager or Cards (which changed in XE16).
EDIT
I've tried removing the third-party progress bar, but that doesn't seem to have any affect - still the same error.
I've also updated to Android Studio 0.5.5, no luck deploying from there either (as opposed to running gradlew installDebug from command-line). Also tried removing /libs/gdk.jar since this isn't required in Android Studio 0.5.5, still no change.
If you have any <uses-library> elements that aren't supported by Glass in your AndroidManifest.xml, you must include the android:required="false" attribute, or remove the element completely, for your app to install on XE16. This is a change in behavior from XE12.
According to the Android docs:
If <uses-library> element is present and its android:required attribute is set to true, the PackageManager framework won't let the user install the application unless the library is present on the user's device...The default android:required value is "true".
I borrowed code from a normal Android app for my Glass app, and I had a leftover element buried in the manifest:
<uses-library android:name="com.google.android.maps"/>
Since I didn't include the android:required="false", XE 16 is correctly preventing the app from installing.
Apparently XE12 didn't enforce this, and installed the app anyway.
After either adding the android:required="false"attribute:
<uses-library android:name="com.google.android.maps"
android:required="false"/>
...or removing this <uses-library> element completely, the app now installs correctly on XE16.
I'm trying out this new thing... It's called conciseness. I've only been reading about it though, so bear with me.
Installed the templates for cocos2d, cocos2d-chipmunk, and cocos2d-box2d and they're showing up in the project window in Xcode. (I understand cocos2d doesn't yet support ARC, which I have enabled.) Trying to build and run a simple Hello World app in any one of the templates results in a "Lexical or Preprocessor Issue - 'FontManager.h' file not found" error. Looked diligently for an answer to that issue and all I got was this, which doesn't end up helping me, but you're welcome to check it out:
cocos2d error
Abandoned cocos2d and went the kobold2d route. Used the installer and that seemed to work fine. I've been able to get projects to build successfully with kobold2d. Problem is, there is next to no literature on it both in print and online.
I thought, "Maybe I should go the cocos3d route instead and just use it for 2D only." Followed this tutorial:
http://www.techipost.com/2011/02/20/installing-cocos3d-for-iphoneipad/
According to everything that's printed out in Terminal during the install process, it should have worked successfully. Unfortunately, I can't get the 3D templates to show up in Xcode.
I'm at my wits' end, here, and I'm thinking about just learning OpenGL and the UIKit over the course of the next, I don't know, year or two?
Is cocos2d even a viable option anymore, post ARC? Thanks any help you can give, guys.
cocos2d is fine, and ARC compatible for versions 1.1 (beta) and 2.0 (beta). I've been working with the 2.0 beta for a few months now, and its excellent. I'm guessing you tried to work with the 1.0.1 stable release which, as you said, is not ARC compatible.
I would recommend downloading 2.0-rc1, installing its templates from its root directory via ./install-templates.sh -f (-f forces overwrite, just in case.)
Blog post on the 2.0-rc1 release: http://www.cocos2d-iphone.org/archives/1885
EDIT:
Just to clarify we're on the same page... I'm going to do a mini outline of the steps:
Download and extract 2.0-rc1
Go into Terminal, navigate to 2.0-rc1's extracted root folder
Fully Quit all instances of Xcode
Type this into console and press enter: ./install-templates.sh -f
The results in Terminal look like this: http://pastebin.com/AVWKv3w1
Re-open Xcode, click New Project -> click iOS or Mac OSX -> click "cocos2d v2.x" -> click "cocos2d iOS" or "cocos2d Mac" -> click Next
Here is where I'm confused: My templates show no options for ARC enabling the project.
Regardless of ARC, enter a project name -> click Next -> select directory -> click Create
After project finishes indexing, select "iPad 5.1 Simulator" or "My Mac 64-bit" as target, and Build (CMD + B) the project, and it complains about FontManager.h?
Just wondering, are you creating a Mac or an iOS project?
Anyway let me know how it goes. =( This is odd!