Using an arbitrary Windows machine (2000/XP or later), I can
install Eclipse CDT to a USB drive
move that USB drive onto a different
Windows machine--one that does not
have any form of Eclipse software
already installed, and potentially a different version of Windows (but 2000/XP or later)
use Eclipse to develop application-level C/C++ programs on that second machine (and that includes using the debugger), running directly from the USB drive without copying anything to C:.
I can do all this without having Administrator privileges on either machine.
I can do the same with NetBeans, and with several other IDEs that support C/C++ development.
Is it possible to do this with any version of Visual Studio Express?
If not, can you explain the technical reason(s) this doesn't work?
Eclipse is apparently designed to be what Microsoft calls an XCOPY deployment...meaning that it doesn't require any special entries in the Windows Registry (or any other "installation identity" on the target machine) in order to work properly.
Visual Studio is most decidedly not designed like this. It makes extensive modifications to the registry during installation, and those entries (and any other resources like special folder locations) will be missing on any other computer.
So you might be able to install Visual Studio on a thumb drive, but some artifacts of the installation will be put on the C: drive, and you will only be able to use the thumb drive with that machine.
Maybe you could install VS Express in a VM running from the USB drive using Portable VirtualBox or VMPlayer. Not the best performance but its usable for not too big projects or learning.
It can definitely be done! I've seen a technician with a copy of it on a USB stick. the only visible flaw was that when you run on a different PC it requires you to enter the license. I could not see any other problems (speed/debugger etc. it all worked on his copy).
check this out:
http://technet.microsoft.com/en-us/appvirtualization/dd334515.aspx
I believe the virtualized package I saw was made by this means:
http://spoon.net/Studio/
Unfortunately it would be matter of experimenting with it...
No VM or extra software was needed!
Related
I'm encountering the following
System.Runtime.Remoting.RemotingException error when I create a blank
Windows 10 Universal Application...
Following are event viewer screens...
I have checked online for other solutions and have already done the
following...
Uninstall/Repair Visual Studio 2015 Update 1
Reset my Windows 10 PC 1511 update
Cleared the Designer/ShadowCache folder
Target environment has been set to x86/x64
Target framework set to 10240
Developer mode enabled
Updated graphic drivers
Have cleaned and rebuilt solution
Updated to VS15 Update 2
Please let me know if you have been able to find a solution to the above
UWP applications fail to launch from Visual Studio if project location and Windows Store apps installation path are on a non-default drive. Also, the XAML Designer will crash if you install Visual Studio and Windows Store apps to a non-default drive
Windows 10 allows users to change the default storage location of Windows Store applications. If you select a non-default drive for your apps, and if you install Visual Studio 2015 onto this drive, the XAML designer will not start and Windows Store app projects built on this drive cannot be run from Visual Studio.
Note: the workaround below will make any Store apps installed to the secondary drive inaccessible until next restart.
The file system driver can be temporarily disabled by running the following command from an admin command prompt:
fltmc detach filecrypt :
This will enable both running apps from this drive as well as usage of the XAML designer until the machine is restarted.
For a longer term fix, move your app or Visual Studio install to your system drive, or a secondary drive that has never been the storage location for Windows Store apps.
I had the same problem. I started visual studio as an administrator and the designer came back.
You might want to try to clear the XAML Designer Shadow Cache. I've fixed al sorts of ailments with this process.
Its been a few months but I have finally been able to get the XAML Designer to work.
As #peterfaraday mentioned, the XAML Designer only works if you install Visual Studio on the System Drive (C: in my case) instead of using any other drive.
After uninstalling Visual Studio keep the following things in mind...
If your system partition is small, look to increase the space as the installation can take a lot of space based on the components selected.
If you had already installed VS on any other drive, while reinstalling you will not be able to change the default installation directory.
This is because your initial path of installation was saved as in the registry. I tried solving this issue by following these steps. In my case I had found multiple keys in the registry and hence "Reset this PC" (Windows 10) by allowing only for my personal files to remain. This cleared out all the registry keys and I was able to install VS back on the C: drive, resulting in the XAML Designer finally working (Please note that resetting your pc will remove any applications installed on your machine)
I got the same problem months ago. I Cleared the cache and Rebuild the solution. I got success.
I am developing a VB.Net based Windows8.1(10) Store application.
After published, I've found out that my App crashes on Windows8.1 while it works fine on Windows10.
So, I want to debug my App on the Windows8.1. However, I cannot find how to do so.
When I [Run] the App to [Simulator], it runs on clone of my computer, but I want to run it on other version of Windows.
Visual Studio 2015 is now installed on Windows10.
Thanks.
Disclaimer: I work on Visual Studio, though not on the Universal/Modern App area.
This is not a supported scenario and there is no feature present in Windows that emulates or simulates previous versions of the "Modern" runtime environment.
The Simulator feature is actually a local-loopback Remote Desktop (Terminal Services) session and existed to make it easier to debug Modern applications given that they could only run in a fullscreen mode, however as this is no-longer the case (as apps are now floating windows) the utility of the Simulator is limited, and as you're discovering is not relevant to your problem.
The only solution I can recommend is to use Hyper-V (or another desktop virtualisation product, such as VirtualBox or VMWare if you don't want a hypervisor installed) to install a dedicated Windows 8.1 environment followed by installing the Visual Studio Remote Debugger.
Given the rapid adoption of Windows 10 (as it is provided as a recommended update to the majority of Windows 8.1 users) I don't personally recommend explicitly targeting the Windows 8.x "Modern" app environment unless you know you will have users or if it's a contract requirement.
Given that the iOS emulator only runs on OS X, what are reasons that people do MonoTouch development on Windows? They offer MonoDevelop for both Windows and OS X.
Some people prefer Visual Studio. Some teams may have invested in tools (like ReSharper, etc) that run in Visual Studio. And teams that maintain other .NET projects may not to switch to Macs as their primary environment.
The idea of only being able to place an app using ONLY the mac tools is not ENTIRELY correct. You are completely able to use the iTunes connect website https://itunesconnect.apple.com/WebObjects/iTunesConnect.woa/wo/4.0.0.7.3.0.9.3.1.1 to place apps on the app store, and you only need the xcode tool for stuff like using the simulator and other options such as that. The reason why people do things such as program on a Windows is because some people are more native with the way the UI works on Windows than on a Mac, as they are quite different. The Windows is more visual, and it offers a simple way to get to things; although the Mac is more user friendly when it comes to the way applications are handled in the core of them. Also, people don't always want to pay the 1200+ price for a Mac machine, when yet they can spend 200+ on a simple Windows OS machine, and still possess the same kind of options. Another thing, you can always run Windows through a mac, so it's kind of a positive negative situation in almost any circumstance.
Hope this helps!
My personal reasons for using Visual Studio currently for my iOS development are:
I'm doing mixed-client-and-server development, and have a single solution with several project types which Xamarin Studio doesn't yet support - or which it only partially supports:
Portable Class Libraries
Azure website projects
WindowsPhone projects
WindowsStore projects
Resharper and the Visual Studio productivity tools and are key parts of my toolchain - they really do make me more productive. (There are other tools too which I'm more familiar with on the PC - e.g. even things like notepad++ and Paint.Net)
Because of my last 20 years on Windows I'm faster at working on the PC - although I am getting quicker at using the Mac.
I'm using the Crystal Report 10 viewer ActiveX control in an Access App I've written. Works great in Office 2003 on 32bit versions of Windows. The problem arrises when I try to run the program in 64 bit Windows (with 32bit Office). I get the following error:
Run-time error '429': ActiveX component can't create object
I get this error on the following line of my VBA code.
Set rdApp = CreateObject("Crystalruntime.application.10")
How can I get this to work in 64bit?
I don't have any specific experience with Crystal Report, but I do have some experience with installing components on a 64-bit Windows environment that were intended for 32-bit Windows, so here are some general suggestions of things to try:
Before installing, try loosening the security privileges - I have Windows Server 2008; on this OS, they're under Start | Administrative Tools | Local Security Policy. Many old installers are thwarted by these controls. You'll want to return them to their defaults after the install.
Make sure that you run the installer with admin privileges (right-click; run as Administrator).
Examine the installation log for Crystal Report - it may indicate a failure registering a component. In one instance, I was able to get the installation working by running the command to register the failed component manually, on an administrator-privileged command line (the command was in the log).
If acceptable, try to create a Windows Virtual Machine running a virtual Windows XP, and try the installations there (this might be a bit tedious, due to your need for MS Office).
Take a look at VMWare's ThinApp - this is intended for packaging applications for administrators, but this was the solution we ended up using to shield one of our 32-bit apps from Windows 64-bit perils
Hope this helps; we struggled for awhile trying different things to get our legacy apps working on a 64-bit environment.
Does windows 8 supports visual source safe (or the other way around?)
Aka, can you install visual source safe running windows 8?
My advice is, don't go closer to Visual SourceSafe than you can spit a rat. VSS has NEVER worked right. Data corruption is all too common. When I worked as an independent consultant to Microsoft in the late 1990's and spent some of my time in Redmond, I found out MS's little secret. Virtually none of the Microsoft development projects used their own VSS. Their internal source code control in the early '90s was a customized version of the old RCS file-based system. They then bought source code rights to Perforce and created a customized version of Perforce for their own use. Now, at least since Visual Studio 2012, they only officially support their own Microsoft Team Foundation Version Control (TFVC) and Git. Support for only those two has been built into VS 2012 and newer IDEs.
Again, even the Microsoft programmers joke about VSS being a "code destruction device." If you already have a honking lot of projects in VSS 6 (which IIRC was built in 1998 and discontinued in 2006), you might want to track down the upgrade to VSS 2005, which is rare, but at least "supported" to whatever degree until sometime in 2017. I also have no idea if either is compatible with Windows 10 (I've installed 6.0 on Windows 7) I'm not sure it's any better, and Microsoft makes it very hard to find full or upgrade downloads of VSS 2005 on their site, but I recall seeing a link for it on one of the MS forums. Search for it.
OTOH, if you are not welded to VSS and don't want to use either TFSC or Git, Subversion (standalone) is a very good alternative (CVS is a dead issue and is not being supported). My current client has development teams using either Git or SVN for their .NET (yuck) projects.
DISCLAIMER: My personal experience (as StackOverflow wants to see for opinion posts) covers 40 years as a top-level software design and development consultant for primarily Fortune 50 companies, during which I have used extensively just about every major COTS and open-source make utility, bug-tracker, and version-control system available. I was a primary beta-tester for the original PVCS (Polytron Version Control System), later bought by Borland. I have also written a proprietary text delta-based version control system for Dow Jones in the early '90s.
We've got it to work.
When it says you'll have to close all running program's it isn't just being nice.
Yes, and in windows 10 too.
Copy and paste VSS from other computer in any folder in new computer.
For register in VB60 ide, execute SSINT.EXE
Find an run .EXE in VSS folder for other opcions
Yes. It can be installed in Windows 10 computers too.