{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 ゆ 、 Hurt° 的问题《Does Surface Pro 3 run Visual studio , sql server》','https://www.manongdao.com/q-937964.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I want to know if Surface Pro 3 i7 - i5 could run any of the following applications
such as :
- visual studio
- SQL server management-studio
- xampp
- Dreamweaver
and so on ..
相关问题
- sql execution latency when assign to a variable
- How to know full paths to DLL's from .csproj f
- Importing NuGet references through a local project
- What is the best way to cache a table from a (SQL)
- Visual Studio 2019 - error MSB8020: The build tool
相关文章
- How to show location of errors, references to memb
- Entity Framework 4.3.1 failing to create (/open) a
- How to track MongoDB requests from a console appli
- Web Test recorder does not allow me to record a te
- Code for inserting data into SQL Server database u
- Visual Studio Hangs on Loading UI Library
- How to use Mercurial from Visual Studio 2010?
- The program '[4432] iisexpress.exe' has ex
Surface Pro 3 with the i5 or i7 processor runs Windows 8.1 and can run these applications, just like a regular laptop or desktop. This should not be confused with the older Surface RT. I run SQL Server and Visual Studio on my Surface Pro 3 but can't speak from first-hand experience about xampp and Dreamweaver. I would expect those applications to run too.
The only issue I've run into is that the optional keypad stopped working after Hyper-V was enabled (needed by Visual studio for mobile device emulation). I simply disabled Hyper-V as a workaround since I don't do mobile development on the device nor have a need for virtualization. I suspect a firmware bug. This may have been fixed in the January 2015 firmware release (which Microsoft pushes via Windows update) because I just re-enabled Hyper-V and have not yet had the problem.