I'm trying to run appcelerator studio in my Desktop.
AMD Athlon II x4 640 3.00 GHz
Ram 4gb
64bit win 8.1
120Gb SSD Samsung 840 EVO
so, in my laptop i7 8gb ram etc.. run smoothly.
When I'm trying to start the studio doesn't respond, not even in task manager.
I'm using CLI and work fine..
I can't find any log file. Which appc studio keep in workspace which one I have no create yet because I can't open the studio.
I run the command appc platform to start the studio from the CMD but nothing happens and this message appears:
{"success":false,"description":"platform command usage: appcelerator platform <api> <method/arguments>"}
I uninstalled AVAST and check first the blocked programs, but nothing..
I disabled Windows firewall too.
Reinstalled the studio many times using different versions of node. But nothing.
And of course I tried to come in contact with the appc team but I can't....
I'm thinking about 4Gb ram limitation; if that blocks the program from starting.
I also try to open the program logged in and logout from CLI.
Any idea? any one with the same problem?
I am not stuck in loading screen the studio try to verify my account and communicate with server.
Studio just won't start at all.
I'm sorry for my bad English.
sorry for your issue.
First - I am assuming your running Windows (Linux is no longer supported)
The CLI command your using appc platform does not launch studio. That is used for accessing platform APIs and thus requires you to provide an API to use.
To launch studio from the CMD line on Windows you would need to cd into your Appcelerator Studio directory and run the associated program. When installing studio, we do put an icon on the desktop, which is by far the easiest way to start it up.
Your right about your RAM limitation. While you'll find that studio does "run" it will be extremely slow, especially once you start using the Android / Windows emulators etc. Windows takes up 1-2GB of Ram on its own, leaving very little for any development tools.
Our recommended configuration for Windows machines is:
* Windows 8.1 or higher
* 16GB of RAM
I would also think about a faster proc as well.
We are in the process of updating our documentation on the pre-reqs' as its a bit misleading. While we say 4GB of RAM is suitable, what we are talking about is 4GB of 'free memory' on top of everything else you have running, not 4GB of total system memory.
Related
I am struggling to find information on this. Of course certain features such as docker and hyper-v will not function, but will Visual Studio 2017 be able to be installed and run on a Windows 10 always-connected ARM device? Like, would typical desktop/web development scenarios with .NET/C++/Python work?
Cheers.
Yes, it is possible. I just got a Asus Nova Go and tried it. Compiling and running a basic .net Core app (with an Avalonia UI) worked just fine but there are some limitations and corner cases that hopefully will get fixed.
Visual Studio takes long to launch, and when lauched is not very performant.
I think the Lenovo Yoga C630 is snappier, because of the bigger 8GB RAM and the Snapdragon 850.
If you have any further questions let me know
I am not able to start any of the Mobile Emulators for Windows Phone 10 (version 10.0.10240).
When I start it from the VS 2015, it gets stuck at "OS is starting". In the Hyper-V Manager, I can see the status "Starting (10%)" for the whole time. After some time, the machine is automatically restarted and it gets stuck at "Starting (10%)" again. Then it timeouts again and the emulator shows an error: "The virtual machine cannot be started because the file rdvgm.exe that is required to start the RemoteFX Manager process does not exist". That is weird, because I do have the rdvgm.exe in the C:\Windows\System32.
I have seen that there are some questions with the same error, but they are resolved by fixing the network switch or by killing devenv.exe after it shows "OS is starting". I have tried both, but it did not help. The network switch issue is different (I have seen it on a different computer - in that case the emulator starts correctly, but VS is not able to connect to it). I am stuck at "Starting (10%)".
What can I try to get it working? Windows Phone 8 emulator is working without any issue.
Thanks
The problem was that Hyper-V detected a graphic card which is able to work with RemoteFX (integrated Intel GPU) but the dedicated one (AMD Radeon) was not supported. I was not able to convince Hyper-V to ignore the dedicated one. When I disabled the RemoteFX support for Hyper-V (unchecked it in the Intel GPU setting in the Hyper-V configuration), it started working.
I found this Microsoft technical support desk yesterday. Its an on line chat with their technical people. I don't know if it covers all MS products. I was asking them about Outlook. Could be worth a try. I found it a touch slow at times, but ...
https://www.awasa.microsoft.com/en-GB/consultation/index?id=914801398064643&skuId=0
Hyper-V has problems enabling RemoteFX with some dual gpu graphics cards. Disabling one of the graphics cards in device manager solved the problem for me:
Disable one of the integrated graphics cards in device manager. I disabled Intel (R) HD Graphics 4600 and left NVIDIA GeForce GT 740M enabled.
Reboot Windows.
Delete the existing mobile phone virtual machines in Hyper-V Manager.
Start Visual Studio and deploy your app again.
I'll be honest, with much distress, I performed a complete factory reset. Reinstalled only Visual Studio 2015 Community edition (only with the tools I needed and not any other emulators such as Android), and it worked after setting up Hyper V as instructed via documentation on dev.windows.com
So I have a HP laptop, and as many HP users know it's a nightmare to install Hyper-V on it. But I somehow managed. Hyper-V is running on my laptop and I have all the necessary hardware requirements:
SLAT is enabled
VT-x is supported and enabled
I'm running 64 bit Windows 8.1 Professional
I'm running Visual Studio 2013 Professional Update 3
Hardware D.E.P. is enabled and supported
And yet when I run the Phone Emulator installation I get the following display:
I can't figure out what's going on or why I keep getting the error. Hyper-V is running as shown:
I've spent two days already trying to figure this out and searching on Google for a solution to this problem. Some of the things I've tried:
Flashing my BIOS
Resolving issues with the Realtek BlueTooth driver (this causes issues with Hyper-V)
Reseting my BIOS
Doing a clean install of my whole system
Installing all Windows Updates
Installing all Visual Studio updates
Enabled / Disabled D.E.P.
Any advice is appreciated. If you need the log from the emulator installation let me know and I'll post it here.
Thanks
UPDATE:
I've attempted to install winsows server standard 2012 and tried enababling hyper-v and installing visual studio and the phone emulator there, and that works and I'm able to run the emulators with no problem.
When I tried the same thing back after installing windows 8 again it installs hyper-v but fails to start windows after installing visual studio update 2 with the phone images etc. The only way I can boot back into windows is if I turn off virtualization in bios.
So it turns out that HP Pavilion laptops support all that is needed to run Hyper-V, however it looks as if HP is blocking the SLAT functionality from working properly with Hyper-V thus not allowing it to run correctly. This looks like it's blocked at the BIOS level.
Updating the BIOS doesn't solve the issue.
The way I came to this conclusion is that Windows Server running Hyper-V runs the Windows Phone emulator with no problems, and it's a Microsoft decision to not require SLAT when running Hyper-V on Windows Server while requiring it on Desktop version of Windows.
Seeing how I paid extra for a more powerful laptop to be able to use features like Hyper-V, and to have an experience such as this due to a manufacturer configuration has left a bitter taste in my mouth. Needless to say this is the LAST time I'll ever buy an HP laptop.
Today i tryed to install wp8 sdk and it installed successfully. but when i'm trying to open visual studio my pc going crash and restart every time. I think its mainboard v-hiper problem or something else. my pc informations
Packard Bell TJ75
CPU : I5 430M
Ram : 3 GB
Graphics : HD 5650 1 GB
BIOS : Phoenix Tec. LTD
how can i fix that problem ?
-Thanks,
Sorry for my english.
What is the crash? A bluescreen? And what codes? Does system event log say anything interesting?
I don't think Visual Studio will try to start the phone emulator until you actually try to debug a phone project in it, so I don't see the immediate connection to Hyper-V.
Does your system crash when you open Visual Studio with no active project? That might absolve Hyper-V.
Alternatively, can you create some other virtual machine image (e.g, from Ubuntu or another Windows), and try booting that one? If your host machine crashes when you do that, then it would implicate Hyper-V.
Windows can crash if it gets too tight on system RAM, and 3G of RAM is not very generous. Both Visual Studio and Hyper-V use a lot of RAM, so you might indeed have problems running them both at the same time.
I just bought a MacBookPro (13", 250HD, and 4GB Ram) because, among other things, I would like to write iPhone Apps.
I need, anyway, to use VS2010 so I think about installing Sun Virtual Box (I've used and I like it) to run Windows 7 with Visual Studio 2010 and SqlExpress2008.
Have you tried it? How many RAM GBs should I reserve for Windows? If I assign 2GB to Windows, will my Mac run fine with the remaining 2GB?
Thanks!
I run Windows 7 and VS 2010 in VMWare Fusion on my Macbook. It has 2GB of RAM, and I've allocated 1GB to the virtual machine. It can be a bit slow at times, but not massively
I've been running Windows XP and Visual Studio in a virtual machine on my MacBook Pro for about a year. I've found that allocating 2GB to Windows and 2 to OS X seems to work well. Everything runs smoothly as long as you don't try to run too much in the host OS (don't try running Mail, iTunes, Firefox, etc all at the same time). I've not run into any trouble running a slew of apps in the VM.
All that being said, I've not tried it running Windows 7 and with it's higher RAM requirements I wouldn't be surprised if you ran into issues.