Does anyone use the Windows 7 preview release for .NET development?
Do things like SQL Server Express 2005/2008, VS.NET 2005/2008 work on it fine?
How about IIS?
Any other things I should be taking into consideration?
I've been using Windows 7 as my primary operating system since its beta. It works pretty well with Visual Studio 2008 SP1, IIS 7.5, SQL Server 2008 SP1. I haven't had any problems so far.
i've been using it since the beta build (7000), and now RC build (7100). no issues, maybe some glitches but i can't remember any particular so nothing that makes real problems. oh, forgot to mention - i use both 32-bit and 64-bit on my rather old notebook and recently built desktop machine. both work fine.
VS2008 works ok, 2005 i think has to be run as administrator for the debugger to work, or some glitch it was, but not 100% positive any more what was it..
SQL2005/2008 Express work fine.
haven't tried IIS, the VS built-in web server works fine.
I too have been using Windows 7 (Beta, RC1) with Visual Studio 2008, MySql, IIS 7.5 (and a ton of addons), Eclipse 3.4, and VMWare for running Linux - everything runs very smooth.
It is a dream come true. Really.
I've been using Win 7 64bit for development heavily since beta.
VS 2008 + SP1, SQL Server Express 2008, TSVN 64Bit with a bit of development tools for Office 2007 Add-ins, Azure and Silverlight
There were a few issues under beta, but they were gone after upgrading to Windows 7 RC. Works like a snap.
Related
We have some applications running on data reader devices with windows CE 6.0.
These apps was created with genexus generating C# / .Net Compact Framework 3.5
Genexus will not support this anymore and I´m looking for alternatives to rewrite these apps.
First, off course, i thought about Microsoft, but i would have to use visual studio 2008 (too old, my devices are also, but...).
Than i thought about SharpDevelop, but Compact Framework was dropped in version 4.
Does anyone know an alternative to develop C# for Windows CE 6.0?
Visual Studio 2008 (or 2005) is your only option and that's simply never going to change. Microsoft abandoned the Compact Framework starting in about 2010 and completely in about 2015. Windows CE itself has effectively been abandoned as well. There's simply no market for anyone else to even try to make an IDE for development for systems that have zero future.
I have developed an windows application in Visual Studio 2012 with .NET framework 4. But when i tried to install my application in Windows XP SP3 it shows that the .exe is not a valid win32 application. Please help me to solve.
This could be one of two, or both, issues. First, ensure that you have the .Net Framework installed on that machine. Second, make sure the application is compiled targeting x86 platform. Most likely, it is the the second issue.
i finally finished a proyect i was requested in my university with Lightswitch. Im ready to deploy (publish) next week, and i was JUST told that the people that will recieve the software, are using XP machines. I've read a lot of questions and lots of fixes, to get Lightswitch working on Windows XP, like:
Changing the DumpBin with "editbin vslshost.exe /SUBSYSTEM:WINDOWS,5.01 /OSVERSION:5.1"
deploy it as a desktop application with the services deployed to IIS (i dont think this will work because those are really old pc's)
install all the prerequisites manually and launch the ClickOnce application directly from deployment manifest file (.application)
create a sample ClickOnce application using Visual Studio 2010 OR Visual Studio 2008 with the same name as mentioned in Visual Studio 2012 and publish it. From the published location take the setup.exe bootstrapper and replace the existing setup.exe bootstrapper created using Visual Studio 2012
With all of this workarounds available, i NEED to ask, will this ultimately work? Can someone REALLY tell me that using one-or-all of this workarounds i WILL be able to deploy the application!?
Someone?
The 2-Tier Deployment issue on XP was also addressed in VS 2012 Update 2 IF you upgrade to a "V3" LightSwitch project by right-clicking on the root project in Solution Explorer and selecting "Upgrade Project". This updates the project to the "V3" project system, runtime and will use a much newer publish wizard. The version of VSLSHOST.exe that ships with VS 2012 Update 2 is compatible with XP.
Dave Kidder - LightSwitch team
http://social.msdn.microsoft.com/profile/dave%20kidder/
I have a successfully deployed application using the 3-tiers running as an out-of-browser (desktop app) on XP. Initially I was going to do the 2-tier deployment, but I was unable to get a workaround to work.
So I have one server, which runs IIS as well as my SQL server (OS is Windows Server 2003, but doesn't have to be.)
The client machines range from Windows XP to Windows 7, and I haven't had any special problems with windows XP.
So I can definitely say XP will work as a client. I was unable to get it to run the middle tier (hence IIS on the server) but I didn't try every last idea I found, so I won't say it's impossible.
The two links I found most helpful in the process were
http://blogs.msdn.com/b/bethmassi/archive/2011/03/23/deployment-guide-how-to-configure-a-web-server-to-host-lightswitch-applications.aspx
and
http://blogs.msdn.com/b/bethmassi/archive/2012/03/29/lightswitch-iis-deployment-enhancements-in-visual-studio-11.aspx
Hope that helps.
I have an WPF and SQL-Server Express based app which I want to deploy using VS-2008 setup and deployment project template. I have added Launch condition for Windows Installer 3.1, Sql Express 2005 and .Net FrameWork 3.5 with SP1 but they are not running in order. I mean:
Windows Installer checking
.Net Framework 3.5 sp1 checking
SQL-Server Express 2005 checking
When i built my project and ran on test machine (with Fresh XP installation only) it tried to install SQL-Server Express 2005 first and then failed for windows installer 3.1.
One more thing i want to know how i can run my DB script after installation of SQL-Server Express 2005.
How I can solve these 2 issues.
I don't think your question actually deals with LaunchConditions as the purpose of LaunchConditions is to prevent the installation of a Windows Installer package if certain conditions aren't met. What you are describing sounds morel ike prereq chaining although I'm not certain what tool you are using to author your install and thus which setup.exe to do the chaining.
I'd also look at putting MSI 4.5 in your chainer, MSI 3.1 is very old in the tooth and only applies to Windows XP these days as all newer OS's come with atleast 4.0.
I've written an app that connects to websites APIs and does some things there. It is a app written in C#, .NET 3.5 on a XP OS.
Now I have a problem. Some people reported that this application hangs on Vista, and not on the more new version of Windows (what was the name?)
So I do not have Vista and do not have money to buy this system only to test this one, freeware application. Is there any other way to test my app if it is valid for Vista or is there other way to make sure it will be working? I'm in a blind spot here and do not know what to do next.
Update: I use Visual C# Express 2008
Use a trial version of Vista?
On one of my small projects, I've worked out some miscellaneous bugs by connecting to users over Remote Assistance before. At least Visual Studio Shell Edition (free) will let you attach to an existing process, and probably C# Express Edition (free) as well.
(This was an obvious choice for me, since my program is a Visual Studio extension, therefore all of my users have Visual Studio installed.)