upgrade

I upgrade to Yosemite my Mini Mac (yesterday) and after a long hours (almost a day) the installation was succeeded. I enter in my source code in Xcode 6.0.1 and after automatically install several things (i just saw the message and wait) i can't see the iOS simulators just iOS Device. I check in Preferences but i have iOS Simulator 7.1 checked but i don't have any other simulator and i can't see 7.1 simulator either. Thanks for your help. EDIT **** After install Xcode 6.1 I saw my iOS simulators again in Xcode. I saw a message "installed required components" when first launched the new Xcode

Whats the best way to upgrade from Galileo to Helios whilst still preserving my settings and plugins? Thanks VonC The surest path to upgrade is to make a "parallel" installation: an Helios Eclipse beside the Galileo one you already have. Regarding your settings, you just need to reference the same workspace. In your eclipse.ini , indicate where your workspace is, and you will get back all your projects, workspaces and perspectives just as you left them. Plugins are trickier, and I would recommend: adding to your eclipse.ini a shared dropins directory reference copying the extra plugins from

I have an unfinished application, but I want to address now the future update of it. Suppose my app was upgraded, so when starts, detects that the database schema is outdated. So for each table has to update according to version number to the new schema while preserving all data. I've read somewhere that on Android the SQLite database have some version number, and auto update stuff, but I didn't found an example for this specific issue. How can this be accomplished on an Android app, using SQLite databases? Is there a specific version number per table stored on Android SQLite databases? If so,

I am working on a WPF desktop application and I am deploying through an install file generated by InstallShield Limited Edition. I would like the installer to prompt the user and remove any previous versions of the application before installing the new version. I suspect this is done via the Upgrade Paths option in InstallShield, but I can't get it figured out. Answer goes to an explanation or a link to a decent how-to, tutorial or manual page that answers my question. At the moment, when running the installer, I get: "Another version of this product is already installed. Installation of this

Is there a framework that can be used to enable a C# Windows Service to automatically check for a newer version and upgrade itself? I can certainly write code to accomplish this, but I am looking for a framework that has already been implemented and (most importantly) tested. [edit] Here is a link to a similar question with links to modern projects that help accomplish this: Auto-update library for .NET? stephbu The only way to unload types is to destroy the appdomain. To do this would require separation of your hosting layer from your executing service code - this is pretty complex. (sort of

Symfony 2.7 was released on 30th April 2015 and is the current LTS (Long Term Support) version after the 2.3 version . Maintenance for these versions will end on May 2016 for Symfony 2.3 and May 2018 for Symfony 2.7. Security fixes will be released during one year after end of maintenance for both versions. As suggested by Massimiliano Arione in the announce comments , what are the changes required to upgrade from Symfony 2.3 from 2.7 without having to check all the minor upgrades (2.3 → 2.4, 2.4 → 2.5, etc.)? As reminded by Med in a comment, Symfony2 developers have tried to keep backward

VS2017 has so far correctly converted several project.json / .xproj based projects to the new .csproj format. I would also like to use the new .csproj format with older .csproj projects that previously targeted only .NET Framework (i.e. they didn't work with dnx/dotnet CLI). It seems that even if a project would still only target .NET Framework, the benefits of <PackageReference> and an easily editable .csproj file seem worth the (hopefully not too great) trouble. Is this possible to do with Visual Studio 2017 directly? If not, what manual steps would be required? Mark I'm editing my answer to