Android Studio: Most activity code templates not available - templates

I have removed and installed Android Studio to 0.5.2, updated all my JDK's and basically started from scratch after abandoning development for a while.
I have seen that there are many code templates that a lot of new videos dealing with Android Studio have; however, I don't have them.
How do I get them and install them if needed?

Android Studio is a Preview product (not-yet-beta) and is under heavy active development. There are canary channel releases almost every week. 0.5.2 was released back in mid March and the other templates that you see have been added since that time. If you want to switch to the canary channel and update to the latest canary build (0.5.9, released last week) then you can follow the directions here to do so: http://tools.android.com/preview-channel#TOC-Android-Studio-Previews

Related

microsoft visual studio installer projects issue

I made a laucher application in c++ that use direct 2d and 3d. Now i making a installer for this. I followed microsoft docs and i made it but there is a issue.
I use 'Microsoft Visual Studio Installer Projects' extension to make that.
The issue is if i already installed my launcher with a previous installer msi file, if i rebuilt a new installer msi and try to run it it show me this error
This is the microft docs i followed to make this: https://learn.microsoft.com/en-us/cpp/ide/walkthrough-deploying-your-program-cpp?view=msvc-160
In the future maybe i need make a update for my laucher. It isn't good idea everytime need go to control panel, search and delete the previous application and install the new one manually.
Anyone know how can i make it automatic remove old version and install new one? Maybe there is a better way to create a installer?
Major Upgrade: In order to upgrade properly, you need to use a major upgrade so that your new version uninstalls the old one and then installs itself (this can happen in reverse order too: new version installed and old remnants deleted afterwards, but this is another story). There are further upgrade types, but stick to major upgrades for simplicity.
The message you are receiving is basically because you have a different package code for the new MSI, but not a new product code or version number (or just one of those problems). You need to get the settings straight.
Recommended step-by-step:
Set "RemovePreviousVersions" to True in the project properties.
In the same place: bump up your version number (one of the first 3 digits)
Answer yes when asked to change product code, or do so yourself manually.
Keep the UpgradeCode the same - it needs to be stable across releases.
Rebuild your setups. Clean out your box of old remnants before testing or test on a virtual.
Testing: Remember to simulate your full upgrade process from first version installed to the new one with different version numbers for a few core files and also try to add a few files and such things. Very important to verify.
Heads-Up: Before ending, it is standard procedure to warn about the potential limitations of VSInstaller Projects (shorter list form).
MSI Tools: Here is a short "review" of other MSI tools.
MSI Upgrade Types: Shamelessly stolen from the InstallShield help file (towards bottom):

TFS 2017/VS 2017 unshelve to different branch, alternatively create a branch from "Main" with saved, uncommitted changes

This describes a scenario that I find myself in now and then when I realize I should have worked in a development branch in TFS. Then I would like to shelve my changes and unshelv into a dev branch, alternatively create a branch from "Main" with saved, uncommitted changes.
What is described on this linked page and many other pages is possible with earlier versions of VS and TFS using the TF power tools command utility:
http://geekswithblogs.net/TarunArora/archive/2011/06/06/unshelve-shelveset-created-from-one-branch-to-another.aspx
Now those features are no longer available, because "most of the previous Power Tools have been integrated into TFS 2017" (according to https://learn.microsoft.com/en-us/visualstudio/releasenotes/tfs2017-relnotes ). But there is no command line utility AFAIK available to enable such operations.
How can I achieve unshelving to another branch with Visual Studio 2017 and TFS 2017?
Alternatively, how can I create a branch from "Main" with saved, uncommitted changes?
With older versions of Visual Studio (2015 and older), the Power Tools extension (https://marketplace.visualstudio.com/items?itemName=TFSPowerToolsTeam.MicrosoftVisualStudioTeamFoundationServer2015Power) used to unshelve to a different branch. But unfortunately this tool does not exist for VS2017.
I have tried another extension MutliMerge - https://marketplace.visualstudio.com/items?itemName=Jesusfan.MultiMerge2017&ssr=false#overview
I was able to unshelve from a branch to a different branch.
I have ensured that there were no pending changes and both branches were up to date.
Note: the tool did not automatically show me the target branch but I was able to edit it and get to work.

Is there an autosave feature in Visual Studio 2017 to deal with its bugs and crashes?

I used to deal with this when I was working with Adobe AfterEffects. It was (and maybe still is) so buggy that it could crash at any moment. So instead of fixing their buggy code-base their developers added a feature that would periodically auto-save all solution files into a separate (copy) folder. So after a crash you could recover some of your work. (Mine was set on auto-save every minute.)
So I've recently switched to using Visual Studio 2017 to develop my C++/MFC projects. (Before that I worked with somewhat older VS 2008 that used to crash very rarely.) But now VS2017 crashes pretty much every day. And if I forget to click save, it literally takes down last 10-15 minutes of my work, if not more.
I tried reporting this to Microsoft (back in summer of 2018, 6 months ago.) Some of my reports were either closed right away when they needed more proof and I didn't have time to deal with their laziness to read my entire post, but some that were accepted are still open and were never fixed. So I'm done submitting bug reports through that portal.
My only recourse at this point is to ask if there's an auto-save "feature" in VS2017, similar to what Adobe did to their AfterAffects?
Anyone wants to crash it right now? Here's just one bug. Create new project -> Visual C++ -> MFC/ATL project -> MFC Application. Then go to Resource View -> Add Resource -> Accelerator. Then click on "None" where I pointed with an arrow:
Is your VS2017 still running after that?
You can find a plugin in the market that does the job.
https://marketplace.visualstudio.com/items?itemName=fluffyerug.Autosave2017
"Auto Save File" extension has more installs and better reviews than the extension from fluffeyrug.
https://marketplace.visualstudio.com/items?itemName=HangjitRai.AutoSaveFile

Visual Studio 2017 blank project open dialog and hang

I installed 2017 and used it for some time (months). After one of the updates, I started having trouble in the file browser window not navigating to other folders without hanging. I can't navigate or choose a file. the app is hung here. I have left it up for several minutes and it stays hung there. I have to kill it from Task Manager in the current version; in prior versions it hung the system and I had to power off. I saw similar problems posted and a reply that indicated it was reproduced and would be fixed. I starting using VS 2015 again in the meantime. That was a few release ago. I had hopes that the most recent one (now on 15.7.3) might fix it since it was fairly large. It made me have a different issue in the same dialog. Now it is blanked out and only VS 2017 is hung. That's a little better since I don't have to restart my system every time I try to run it. But I really need to move to VS 2017.
Any suggestions would be appreciated. I have uninstalled and re-installed several times and tried uninstalling and reinstalling the more recent .net versions.
Windows 10 Enterprise, kept current with Windows Update, 32G RAM
On trying to browse for a solution, this comes up.

VS2010 Intellisense problems

This question actually is an implicit answer, since I could fix the problem in the meantime for myself. But I wanted to publish my experience, since some other developers might have a similar problems.
The problem:
I am using VS2010 prof SP1 on Windows XP SP3, pure C++ only. (AntiVirus software present).
Since some days Intellisense - which is quite helpful under normal conditions - does not work anymore.
Things tried:
created a new simple console application. -> Intellisense still not working.
resetting VS-Settings by means of Tools/Import & Export Settings/Reset. -> Intellisense still not working
Changes to option settings in Text-Editor/C++/Advanced inclusive logging did not help.
-> Intellisense still not working
There was actually an interesting observation:
Intellisense normally creates a directory 'ipch' in the solution directory to store intermediate files. In my solution folders it disappeared as soon as the solution was opened. When I created a folder 'ipch' and opened the solution Intellisense removed the folder again - strange.
The final fix:
During the last week some new Windows updates were installed. I noticed some other unusual behaviour of my PC as well. After having created an image of my PC, I decided to
uninstall Windows updates from 2013-09-11 (4 packages) and one update from 2013-08-28.
(unfortunately I did not note down the KB-numbers)
AND: out of a sudden Intellisense is working again !
Maybe this report could be helpful for some other persons.
Automatic Updates are now disabled on my PCs.
Confirmed 100%
Microsoft Visual Studio 2010 Version 10.0.30319.1 RTMRel
Microsoft NET framework 4.0.30319 RTMRel
Microsoft Windows XP Professional Version 2002 Service Pack 3
Intellisense stops working after installing KB2876217.
Intellisense is back after removing update.
I had the same problem and also had the idea that one of the Windows Updates is buggy, so I can confirm your report.
I tried to uninstall them one-b<-one and found the "bad guy":
KB2876217 destroys intellisense for VS2010 under XP SP3.
A supported hotfix is available from Microsoft to fix this issue. Check at http://support.microsoft.com/kb/2526044/en-us
Actually, it may not be such a good idea to uninstall update KB2876217. Instead, install Visual Studio SP1 update (if not already installed) and then install update KB2526044. I have tried it before and it does work...