Scenario: A Windows 7 machine running VMWare Server as a host for a Windows 2008 R2 guest OS.
Problem: Slow performance transferring files to/from the guest OS.
Solution: Performance issues with bridged networking on Windows Server 2003 and Windows 2008 host operating systems. (It worked with Windows 7 too).
I was trying to add a new COM DLL to my VS2010 project but it kept giving me the following error message:
A reference to the “….dll” could not be added.Please make sure that the file is accessible and that it is a valid assembly or COM component
Then I realised I hadn’t registered my self-registering assembly on my machine as this was a new machine and the first time I had used this project. Since I had my VS Command Prompt open I ran RegSvr32 on the assembly and waited for the usual message. Instead it threw me an error and I was left to try and find out what was causing the problem. As it turns out the solution was relatively simple. I needed to run my command prompt as the administrator to get RegSvr32 to work as I am using a Windows 7 OS. Now my COM DLL is registered and listed in the COM tab of the Visual Studio Add Reference dialog.
How do we stop those trigger happy web users who feel the need to press buttons more than once. One way is to disable/change the button on the first click. All that is required is a couple of simple lines of code to make this happen. In my Page_Load event I have the following;
if (!IsPostBack)
{
MyASPNetButton.Attributes.Add("onclick", "this.value='Please wait...'; this.disabled=true;" + Page.ClientScript.GetPostBackEventReference(MyASPNetButton, "").ToString());
}
If your web services are running on a server that is not in the DMZ and you are not able to open port 80 to these services either then you will encounter a common scenario. Your Silverlight application will not be able to connect to these services because it can’t get to the clientaccesspolicy.xml file that is required to access services on a different server to the one that served your Silverlight application.
If you hosting your Silverlight application on a machine running IIS 7.5 (Windows Server 2008) then help is at hand – click here for more details.
This is a bit more of an unusual situation that I found a fix for.
I had set up my Windows 7 x64 machine so that I could connect to it remotely. When I got to work I tried the connection from the Windows XP (SP3) machine that I had been given to use. It was at least running IE8 but when I fired up the connection to the remote machine IE crashed, told me I needed to report the error then recovered enough to let me know it could not connect to my remote machine.
A quick bit of surfing later and the answer appeared in the form of this answer from Microsoft.
Apparently I didn’t have IPV6 installed on the machine, but doing the installation solved the problem.
GP23 Consulting 