That would consume the WebClient by you, or you would need to include a WebBrowser control. Which also would make the HTTP requests to your desired web page (which is the Google Wallet API web page). You know this is a cycle that starts and ends at the very same point, the System.Net namespace.
I would go with programming my own control and getting the response from the server using either a WebClient, or by downloading the response stream.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
I am getting the following error after uploading the file to the host:
Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/jassimuser/mybluefile.com/login_user.php:1) in /home/jassimuser/mybluefile.com/includes/php_header.php on line 3
Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/jassimuser/mybluefile.com/login_user.php:1) in /home/jassimuser/mybluefile.com/includes/php_header.php on line 3
Warning: Cannot modify header information - headers already sent by (output started at /home/jassimuser/mybluefile.com/login_user.php:1) in /home/jassimuser/mybluefile.com/login_user.php on line 52
An SSL certificate will usually have the "key usage" restricted to "server authentication" (and possibly "client authentication"). That means you can't use it for code-signing, email protection, time-stamping or OCSP signing.
In theory a SSL certificate can be used to digitally sign files/code, however it depends on the properties of that SSL certificate...
The SSL have to have keyUsage.digitalSignature flag to set to use it for file signing, and extendedKeyUsage.codeSigning for code signing...
As you bought the SSL for web site (probably via your host) you will not have these flags set...
You may ask to extend the certificate or get a new one for file/code signing...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
It's a lot of verbose HTML to write...
(not to mention the need to write unique id by hand)
Really what I would like to, is torture KnockoutJS[^] or VueJS[^] (please, no AngularJS... unless you have a fully working sample! ) so that I can create some sort of component that I can initialize like that (i.e. data binding optional! i.e. not mandatory! inline html in my sample!)
then put those header/content template somewhere else....
then make sure somehow, that the argument interface is easy to guess / know (for my future self) (maybe WebComponent + TypeScipt can help? such as with my Knockout Grid[^]?)
While acceptable... it's a little cumbersome...
my challenge today was to improve those tools, to implement an elegant (and NOT particularly data bound) declarative markup like:
I got it working! yoohoo!
I still dunno how I could create such component in a stream lined fashion... That is the question I would like to resolve!
But KnockoutJS templating is NOT the way to implement this elegant markup syntax!
I've converted to writing all of my applications for my company as web applications because:
1) Much easier to deploy. (Just update the website)
2) Works out better for remote users
3) More secure. If a laptop is stolen, lost or employee is terminated, their network access is denied so they can no longer access corporate data.
I'm sure there are other "pros" you can think of ...
Regarding developing "rich" user experience, have you considered using 3rd party controls ?
I have been using WinForms controls from Developer Express for the past 6 years and found that their products and support are excellent.
I have attended 2 of their Road Shows and met with their engineers and they are very friendly and helpful.
I don't want to violate and posting rules and I do not work for DevExpress, but I do highly recommend looking into their tools.
Here is an argument from the other side - I prefer desktop applications.
I took our organisation to Silverlight because the result was almost as rich as winforms which we were using. This was a brilliant move right up till Microsoft killed Silverlight. Do NOT get me started on that decision!
Since then we have had a senior dev trying to duplicate the functionality of one of our apps using MVC/SP and Telerik controls. He is failing.
He is also of the opinion that development time will be at least double using the current web stack (we have excellent Silverlight skills that transfer directly to WPF).
Web deployment is simpler and if you have remote or international users it makes sense to use a web platform but for local, internal apps I would use desktop and clickonce.
Never underestimate the power of human stupidity
Last Visit: 31-Dec-99 18:00 Last Update: 25-Oct-21 19:45