Comments for RobinDotNet's Blog

Comment on About Me by Denis

Denis — Fri, 17 May 2013 15:02:40 +0000

Robin,

Thanks for your response. I just got it today. As it happens I broke down and paid Microsoft to troubleshoot it for me. Well, it wasn’t a problem with my program, per se. The issue was with Microsoft SqlServer Compact Edition. I had it setup to install locally with my application but it was intermittently crashing on 64 bit machines because of a known (but rather poorly documented) issue with Microsoft SqlServer Compact Edition. Fortunately, after we identified the problem I was able to find a very helpful blog post that had detailed instructions for properly setting up Microsoft SqlServer in my project. Problem solved. I have installed the new build on five machines (XP, Vista, 2 Windows 7, and a Windows 8) and all performed as expected. My fix has now been released as an update to my customers.

Best Regards,

Denis

Comment on Windows 8 and ClickOnce : the definitive answer by robindotnet

robindotnet — Thu, 16 May 2013 16:32:18 +0000

Do you get the PF File not found exception when building, when running, or (only) when publishing? If it’s when building, I’d post it to the C# or VB MSDN Forum. If it’s when publishing, I would post it to the MSDN ClickOnce forum.

Robin

Comment on How to install IIS Application Request Routing in Windows Azure by robindotnet

robindotnet — Thu, 16 May 2013 16:30:49 +0000

Hi Carl,
Thank you for your feedback. In my experience, the msi packages ignore the /wait when running in a batch file, and I couldn’t ensure that the first would finish before the next tried to run, which is why I put in the ping to make it wait. I had repeated failures when trying it with /wait. Also, when you say Azure VM, is it a VM you’ve spun up yourself, or is it a cloud service? (Mine is running in a cloud service). Only other thing I can think of is they changed it in Windows Server 2012.
Robin

Comment on How to install IIS Application Request Routing in Windows Azure by Carl Stinson

Carl Stinson — Thu, 16 May 2013 13:44:01 +0000

Testing (local desktop and on Azure VM) with start /wait in batch files looks to work as required. It’s a lot cleaner than the PING wait hack too.

Comment on Windows 8 and ClickOnce : the definitive answer by Florian

Florian — Thu, 16 May 2013 11:20:50 +0000

forget the first section. didn’t read the second article

Comment on Windows 8 and ClickOnce : the definitive answer by Florian

Florian — Thu, 16 May 2013 09:49:48 +0000

Great article for signing click once, but I have signed my WPF Application with a code signing certificate from godaddy and it shows it as signed. BUT I still see the smartscreen window. Is there any why how to get this not to show up.

ehm. OT: You may can help me a PE File not found exception I’m getting all 3-5 times I’m publishing the application.

Thanks alot

Comment on Windows 8 and ClickOnce : the definitive answer by Saurabh Nandu

Saurabh Nandu — Mon, 13 May 2013 19:50:40 +0000

wonderful blog… saved me a lot of time. Thanks a ton!

Comment on Windows 8 and ClickOnce : the definitive answer by robindotnet

robindotnet — Mon, 06 May 2013 06:03:07 +0000

If you are working for an enterprise and your system support guys are creating their own valid certificates, then yes, that should work. I see that case so rarely, that I assumed you were using a test certificate created in Visual Studio. Sorry about that. There is a second bit that comes into play, especially if you have a new certificate (or one not known to Microsoft). There is a "reputation" that is determined based on the number of installs for an application signed with a specific certificate. There's some combination used by Microsoft in their algorithm for deciding whether to display the SSF or not. At some point, enough people will have installed the application to build up the reputation, and the SSF will no longer be displayed. I mention this in the follow-up blog entry after this one. Robin

Comment on Windows 8 and ClickOnce : the definitive answer by Anonymous

Anonymous — Thu, 02 May 2013 20:41:15 +0000

If an end user or a group policy administrator installs the publisher’s certificate into the Trusted Publishers store and the issuing certificate into the Trusted Root certificate store, SmartScreen Filter should not prompt the user for ANY reason, as they have already “clicked” their consent to trust the publisher by having installed those certificates. That is the problem. I’m sorry you couldn’t understand the extended metaphor. If an organization chooses to issue its own code signing certificates for use inside its own organization, and installs those certificates in the Trusted Publishers store on its own computers, what right does Microsoft have to tell the organization that it should not trust the organization’s own in-house developed software?

Comment on Windows 8 and ClickOnce : the definitive answer revisited by robindotnet

robindotnet — Thu, 02 May 2013 19:12:36 +0000

If it says unknown publisher, then either your deployment is not signed, your executable is not signed, or your certificate is not from a valid CA like Verisign. You can check the executable by looking at its properties.