Just a thought here with the off/on thing with windows releases...
Perhaps Microsoft is manic / depressive? the huge swing from a release folks love to one folks hate.... seems to fit the symptoms anyway....
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
it has been a while but as I recall click one can work with non IE browsers.
the "Magic" was that the browser gets a mime type when it downloads the click once startup file and has to send that download to an exe on the client pc to act on.
so any browser should be able to register the type to an installed click once handler and it should work.
I used to have a customer with about 300 sales machines that we updated with click once when we had a new build to release. worked well as long as the client pc did not get borked with virus or other junk.
an old saying goes with that word: assume
when you do that you make an
please do not do that... check the facts or take it as it is.
Huh ? an "Azure Website" is running IIS with a web.config *if* the platform you pick is .net.
"Azure web services api" that is not a thing.
do you mean the API service ?
if we go to the video (as I have not had time yet to do it myself)
one of the demos was to create a web api.... they had a controller and hooked up some code so that the controller retuned data... nothing crazy,
they did say that the api app service has an open source tool that provides json meta-data to help with describing and consuming the api you create.
no dark secret there it's still just iis running asp.net and a nuget package.
get this: azure anything is a vm running windows server or Linux
if you want uber control you can have it by paying for a higher level option and you can rdp into the server and do what you want.
but like any hosting system the lower cost levels give you less admin access so they can make a shared server.
the add on to that is that they have worked out how to swap out vm's manage a lot of servers and make it all as simple as they could for us to setup and manage.
the only part that is different is the thing where they allow you to take a bunch of service calls and hook them together , ok that they did not show a coding session for, possibly that is what you are actually worried about ??
I bet that also can be coded and if you do not like it then do not use it but that is a small part of th whole deal.
Hey real boy figure out the cost if you need to have fail over and scale up, and locate servers in more than one data center, and make sure the same code runs on all the servers ... doing this the old way gets really crazy expensive. The azure way is dirt cheap when you factor all of the costs
Yeah one lone website on one shared host can be cheap but if you are growing and trying to make money.....
Yes there is nothing new, they have azure web api (node.js or c# web api thing). I don't really know what it's called. But it seems like they're expanding on that and adding a logic app.
Cost wise, I figure it's much cheaper to have a website running pure asp.net webapi than an azure webapi project.
Part of the deal with azure is how it handles your traffic on demand. That is how azure is actually cheap. Not to mention all the data centers so you can spin up servers where you need them.
Also if you just want a low cost website they have a free website level that you can use. Check the pricing calculator.
Hmmm great way to create a self-fulfilling-prophecy
if we all declare to Microsoft that we know they do not care etc... and then in our anger / dismay or other reaction tell them how horrible they are then it's a sure bet they will not want to listen.
the two feedback links have one really good example of "saying nothing" they may have a valid point but it's just too general for a developer to use as an item to fix.
sure at some high level some exec could try to cover how to re-work every dialog in windows but that just means that the fix is going to take a ton of man hours to do.
well anyway ..... have a good day and get some rest.
did some checking and it looks like they did update the older pos for .net to support .net 4
so I would see if that will be allowed in a store app
the windows rt api only has two kinds of devices, that seems really odd as normal opos supports a number of types of devices that you need if you are going to do a real POS system.