Entries for ehuna

Is .NET 3.0 RTM supposed to work on Windows 2003 Server? [Is .NET 3.0 RTM supposed to work on Windows 2003 Server?]

ehuna — Thu, 09 Nov 2006 04:33:21 GMT

I downloaded .NET 3.0 RTM today and installed it on my Windows 2003 Server development server.

I tried double clicking on a XAML file and the system went nuts: the screen flashed, the mouse kept moving to the center and corners of the screen, etc...

It looked like my machine was taken by the Indigo/Avalong ghost... Finally I had to bring up task manager and kill IE.

I tried multiple times, with different XAML files. I tried uninstalling and re-installing, downloading the fast installer and the full re-distributable (50 MB). No luck - WPF just doesn't seem to work.

I've been using the same sample XAML files on Vista Beta2 then RC1. I also used it with .NET RC1 on Windows XP SP2 without problems.

I never installed a beta version of WinFX/.NET 3.0 on this machine and waited until the RTM.

Is .NET 3.0 supposed to work on Windows 2003 Server or is this a bug in the installer that it allowed me to install it at all?

in reply to Is .NET 3.0 RTM supposed to work on Windows 2003 Server?

Using MSN for a Remote Desktop Connection [Using MSN for a Remote Desktop Connection]

ehuna — Tue, 27 Dec 2005 01:48:50 GMT

Hello,

In MSN Messenger 7.5 there's an option for sharing your desktop with whoever you're chatting with (Actions > Request Remote Assistance).

Unfortunately, firewalls will by default block the port used by Remote Desktop / Terminal Services, making this request pretty useless.

Instead I have used in the past Citrix products which load an ActiveX control on a web page that then connects to a server. I can then just send the link to my chat buddy, allowing us to completely bypass the firewalls. I can then help someone across the hall or my aunt in France.

Does anyone at Microsoft know of a MS solution for this issue? Specifically a system that is not blocked by firewalls - for example by having the clients connect to a central server. Outgoing connections are generally not blocked.

Also, why not implement something like this in the MSN Messenger platform?

in reply to Using MSN for a Remote Desktop Connection

WinFX that works with today's VS 2005? [WinFX that works with today's VS 2005?]

ehuna — Fri, 28 Oct 2005 00:11:00 GMT

I just saw that the final release (not beta) of Visual Studio 2005 Professional is available on MSDN subscriber downloads.

Is there a matching WinFX beta? VS 2005 RTM didn't have one so I've been stuck with VS 2005 Beta2 since....

Congratulations to Microsoft though for releasing SQL Server 2005, Visual Studio 2005, and the .Net Framework 2.0 earlier than expected! (at least to us lucky MSDN subscribers) :D

in reply to WinFX that works with today's VS 2005?

Is a build server really necessary? [Is a build server really necessary?]

ehuna — Thu, 20 Oct 2005 07:30:18 GMT

Before .Net when our applications (COM, MFC, etc...) needed to be compiled and deployed I always insisted on making sure on the following process:

1) The developers checked in all source code (VSS, Perforce, whatever source control system you prefer).

2) The person responsible for the build would then get the latest source from source control and attempt to compile it.

3) The resulting binaries would then be deployed to QA, and the same build image would then be deployed to Production (whatever that means: a web farm, a master CD, etc...).

The above process has a few advantages:

1) All code is properly checked in (there are no "forgotten" classes, files, etc... lost when the developer's hard drive crashes). In many cases, if a file is forgotten, the project won't compile

2) Any third party dependencies are immediately indentified. For example, if the developer installed a third party OCX on his/her environment the project won't compile on the build server.

3) All compiled binaries created on the build server are "clean" (for example for linked libraries, the correct DLL would be used, and not some strange DLL installed on the developer's system).

Now, with .Net, whatever code is being compiled is really ending up as IL. So for companies with smaller 2-3 development teams, where some developers are also responsible for deploying the apps, does it still make sense to go through a build server.

I understand there are still benefits (1 and 2 above), but if we find other ways to make sure code and dependencies are checked in or documented, would it be ok to bypass the build server all together?

What do folks do at Microsoft? Anyone has any strong feelings either way?

in reply to Is a build server really necessary?

9 guy bean bag from the PDC rides quietly on a LAX bus (Los Angeles, California) [9 guy bean bag from the PDC rides quietly on a LAX bus (Los Angeles, California)]

ehuna — Tue, 18 Oct 2005 06:30:01 GMT

9 guy bean bag from the PDC rides quietly on a LAX bus (Los Angeles, California)

in reply to 9 guy bean bag from the PDC rides quietly on a LAX bus (Los Angeles, California)

Big 9 guy at LAX (Los Angeles Airport, California) [Big 9 guy at LAX (Los Angeles Airport, California)]

ehuna — Tue, 18 Oct 2005 06:28:30 GMT

Big 9 guy at LAX (Los Angeles Airport, California)

in reply to Big 9 guy at LAX (Los Angeles Airport, California)