I've been starting with Python in Canopy Enthought for a little more than a month now. I'm struggling with installation at so many levels it drives me crazy.
I want to install modules to deal with tif files, in order to create multiimage tof, etc.
tifffile 0.4
PyLibTiff
I cannot get them through easy_install.
I tried pip install tifffile
I keep getting these errors:
error: Visual Studio 2008 Express Edition was found in your path, but
Visual Studio 2008 is required to build extension modules on a
64-bit platform.
Visual studio is installed, I installed a 2013 express version, then downloaded and installed 2008 too, nothing seems to work.
This is driving my crazy, and honestly I'm not sure I handle the basics of how python handle the different modules. Through different .zip packages, I ended with the tifffile code, I don't know where to put it. There is a .exe installer for PyLibTiff but I can't get it to work either.
If anybody can help, that would save the life of my computer, I feel like it's gonna learn to fly soon.
Thanks a lot !!
Dam.
You need Visual Studio 2008. Not Visual Studio Express 2008.
Related
I have done the following:
Installed Visual Studio Community 2017 (with all the python tools).
Installed the newest version of IronPython from the IronPython website using the MSI installer.
Opened VSC2017, went all the way to Python, no IronPython project is showing up.
Now I repeated these steps by uninstalling everything and reinstalling 20XX VSC, same thing happens.
I have no idea what I am doing wrong at this point, I've been through every readme and youtube video I can find on the issue.
I have Visual Studio Community Edition 2015 installed on my drive D:.
I recently got a 1TB SSD for my C: drive and wanted to move VS to that drive. Long story shortened; it was a nightmare. Although I could uninstall VS, I could not get it to reinstall in any other location except for D:. After three days of trying, I gave up and reinstalled back to D:. I still could not get it to install correctly and some things are "damaged". Updates, etc. do not completely succeed because of the "damaged" module installation. I do not want to risk running the "Repair" option in the control panel again because that often makes it worse (damages more things); which leads to a several hour process of uninstalling & reinstalling. This question shows some of the installer/uninstaller problems: Installation errors in repair of Visual Studio 2015 Community Edition on Windows 10
I am now planning on reinstalling Windows 10 Pro in order to clean up this install.
I was planning on eventually getting Visual Studio Professional 2015.
Will I have similar problems upgrading from "Community Edition" to the "Professional" version?
I was hoping to open a dialog box, type in the license key and have the "Community Editon" become a "Professional" version. Is that possible or is a complete uninstall/reinstall how this upgrade would work?
(Disclaimer: I worked on Visual Studio 2015 including portions of the setup experience while at Microsoft)
It can, but it isn't as simple as entering an upgraded product key, you also need the media.
When you buy/license Visual Studio 2015 Professional or higher, you'll have access to the install media, usually an ISO file or vs_setup.exe web-downloader. Mount the ISO image and run Setup and you'll be prompted to upgrade (if I remember correctly). You cannot (to my knowledge) have a side-by-side install of Community and Professional Edition (unlike you can with the Express editions).
Personally I would just do a full uninstall of Community first, then a clean install of Professional - when I worked on the setup experience of VS2015 I logged a whole bunch of bugs that were experienced during in-version SKU upgrades (e.g. upgrading Community to Enterprise, then downgrading to Professional), such as project template item templates disappearing, etc. It wouldn't surprise me if these still caused issues - I don't think it's worth the risk.
Regarding Visual Studio 2017
Visual Studio 2017 now fully supports side-by-side installations of different SKUs (which is why the installation directory is %programfiles(x86)%\Microsoft Visual Studio 2017\Enterprise). So rather than doing an in-place upgrade from a lower SKU to a higher SKU, you install it as a separate install entirely. You'll need to manually move your settings and extensions over (or use the Microsoft Account-based settings synchronization feature).
I personally know that when your email address subscription has professional your VS install using that email if community will upgrade on it's own to Pro.
Previously I have Visual Studio 2012 Ultimate version in my system. Its is working fine.
Later I am trying to install 2013 also but it is not installing properly and giving error message like attached image.After that VS2012 also is not working properly. Then I tried to Install Vs2012 also again. But this installation process also giving same error. I can not able to upload image due to reputation.
This is the exact error:
"Visual Studio Core Fetures Fatal error during installing.
Microsoft Visual C++ 2012 Core Libraries Package failed.
Microsoft Visual C++ 2012 Microsoft Foundation Class Library Package failes."
Please help me to install visual studio 2012 & 2013.
Because Visual Studio requires many components to be installed, and if they are not, VS will install them. However, when you uninstall VS, it will not remove these components automatically because it does not record which component is installed by it and which exists before VS is installed. Other applications might need these components to work.
When you uninstall VS2012, you really only remove VS itself. Then you try to install VS2013 and meet an error, and that may be the problem. To make things worse, you did not clean uninstall VS2013 either, which caused the later errors when you try to reinstall VS2012.
You may as well try to clean uninstall VS 2012 and the same goes for VS 2013, just some Google work.
I hope this will help you a little.
I installed Visual Studio 2010 Premium on my Windows 7 workstation. After loading a test C++ project, I noticed that it could not locate iostream. I took a look in C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include and noticed that only two files exist here, srv.h and wmiatlprov.h
I installed the VS2010 product on a test virtual machine, and this directory (...\VC\include) is filled with the usual collection of folders and headers (the materials you'd expect to find in the includes directory.)
I have taken the following steps to rectify the missing headers on the problem workstation:
Verified that I have no A/V software active (I am using MS Security Essentials, realtime is disabled)
Uninstalled Visual Studio 2010 Premium and all other sub-products from Programs & Features
Ran the VS2010 Uninstall Tool with the /full and /netfx parameters
Deleted the Visual Studio 10.0 directories from both Program Files and Program Files (x86)
Reinstalled Visual Studio 2010 from a freshly downloaded ISO from MSDN.
I also completed the above steps, but used a different edition for the reinstall, VS2010 Professional.
So far, nothing above has been able to produce an installed Visual Studio 2010 product with all of the C++ headers installed on my workstation.
Ideas?
The solution to this problem is as follows. It is based on the solution given in
http://connect.microsoft.com/VisualStudio/feedback/details/774158/re-installed-visual-studio-2010-and-c-standard-headers-are-missing
Uninstall Visual Studio 2010.
Uninstall Visual Studio 2010 SP1 (despite the warning it gives).
Open Registry Editor (regedit).
Search for keys named PaddedVersion
Remove any parent keys VisualStudio\10.0\VC\Libraries, or similar (note the version number 10.0, which corresponds to 2010). Delete all of these registry paths. The search for the PaddedVersion key is just to ease up this search.
Install Visual Studio 2010.
Install Visual Studio 2010 SP1.
This solution may not be minimal, but it works for me. Hopefully others can confirm. The important difference here is that it is not just the HKEY_LOCAL_MACHINE from which the registry path must be deleted, as indicated in the link above.
While doing some research on this topic it seems like no matter how you uninstall Visual Studio there are always pieces left behind.
Two options to consider.
Option 1
Install VS 2010 on virtual machine.
Zip needed files from your virtual machine.
Copy and unzip them over to the workstation.
Option 2
Format hard drive.
Install fresh copy of Windows 7.
Install fresh copy VS 2010.
The Visual Studio installer is a fickle beast, to put it mildly. The generic diagnostic is that your registry is dirty, having a record of a sub-component of VS installed while it is not actually present anymore. There are a lot of sub-components and an enormous number of registry entries that keep track of their install state and their config. Finding such a dirty key back is a serious needle-in-a-haystack problem.
This kind of registry damage is very common if you ever had a beta or RC edition installed. I never had a beta version that didn't give me an enormous problem getting the RTM version installed. The VS2010 beta went particularly badly for me, albeit that I shot my foot badly by updating to Windows7 without uninstalling the beta. A gigantic mess, to put it mildly. You can expect similar kind of upheaval of you ever had an un/install that didn't complete. And of course registry damage is always around to turn this into misery.
The problem is quite common, there are Visual Studio cleanup tools around that aim to purge the registry after something like this happened. For VS2010 there are actually several. Google "vs2010 uninstall utility" to find them. No idea if they are different someway, no reason I can think of to not just run them all.
Chips are seriously down when that still doesn't fix the problem. Only thing left is to dig through the dd*.txt files that are left in the TEMP directory after an install. They contain a detailed trace of the installer's decisions. Beware that you'll drown in the amount of data.
I tried several rounds of uninstalling and reinstalling. The hack that finally worked was to copy the entire contents of the VC folder from a machine with a working VS 2010 installation. You probably don't need to copy all of these , but I was missing 3000+ files in include, lib, and other folders within VC.
I ran into this problem on Windows 8.1 when the VS 2010 Web installer failed to install correctly the first time. I followed Kaba's steps above with a slight difference and it solved the problem for me (so kudos to Kaba). The difference is that I deleted all the “VisualStudio\10.0” keys and all its sub-keys, as well as the “VisualStudio\10.0_Config” and sub-keys.
The solution at http://connect.microsoft.com/VisualStudio/feedback/details/774158/re-installed-visual-studio-2010-and-c-standard-headers-are-missing not worked for me.
After Uninstall Visual Studio 2010 and SP1, I used a registry cleaner software CCleaner and installed again. It fixed.
My laptop had an install error with Vista Ultimate and now it does not let me run Visual Studio. I was able to install Visual Studio 2008 on my HP TouchSmart without a problem and now I use it on there. I want to be able to travel though. So I was wondering if I take the folder in which Visual Studio was installed and put it on my external hard drive and just run it off of there. Is this possible? I've managed to do it with other programs before.
No this will not work with Visual Studio. You're essentially asking if Visual Studio is xcopy deployable. It unfortunately is not. It relies on many items which are not simply a part of the install folder including ...
Registry Keys
Certain versions of the CLR being installed
Supporting programs and libraries
And many, many other items.
As others have said, because of the dependencies it is not xcopy deployable. Maybe Virtual PC is the answer to your problems.
You can install VS 2008 on some other drive/older in your computer. Bu VS 2008 needs to run some DLL or other files to run in the OS. So you can not install it.
There are many pre-requisites that are installed with VS 2008, so I think that it's not a good idea.