Re: Debugging AngularJS
Was working on a SPA project last year, built in VS, and all client debugging was done using Chrome developer tools. On Aug 8, 2015 4:15 PM, "Greg Keogh" wrote: > Folks, back to business ... I've done a crash course on AngularJS and I'm > writing a client-side demo app that talks to a Web API REST service. It's > working okay and growing, but I'm using the crude technique of just editing > the html and js files in Visual Studio 2015 without a project. Since VS is > just acting as a glorified editor I can't debug and any tiny stupid errors > in the files just causes everything to stop without reason. > > Are there others here who are writing this sort of client-side app and > have a way of getting a VS debugging experience? What's your technique? > > *Greg K* >
Debugging AngularJS
Folks, back to business ... I've done a crash course on AngularJS and I'm writing a client-side demo app that talks to a Web API REST service. It's working okay and growing, but I'm using the crude technique of just editing the html and js files in Visual Studio 2015 without a project. Since VS is just acting as a glorified editor I can't debug and any tiny stupid errors in the files just causes everything to stop without reason. Are there others here who are writing this sort of client-side app and have a way of getting a VS debugging experience? What's your technique? *Greg K*
[OT] Preparing Windows 10
This is a Friday thing, but for your possible amusement ... I installed Windows 10 retail (inside Parallels on a Mac) and I'm trying to use it in anger for the first time. The first things I did were to disable Windows Defender, uninstall Flash, unpin or uninstall weather, news, email, contacts, store, photos, music, pictures (and others I forget). So after using group policy editor, regedit, elevated command lines, etc I finally stripped Windows 10 back to a typical development machine. Weirdly enough, by the time I cleaned up the Start Menu of junk it was empty ... there are no coloured tiles on my Start fly-out as they were all utterly useless. What a shame, as I suppose whole departments of people went into designing and implementing it -- *Greg*
Re: Web API and https timeout
Haha classic On Friday, 7 August 2015, Greg Keogh wrote: > OK FOLKS! Those of you who are sys admins don't laugh at what I just > found, by accidentally noticing that all of my web sites where slowly > vanishing throughout the afternoon... > > Around 11am this morning I finished migrating 6 of my domains from one > provider to another. I set the DNS A records for all domains to point to my > home server's IP address. However, I transposed two digits of the address > and as a result, all domains slowly vanished as the records were propagated > around the globe. That's certainly why my https test failed, then an hour > later the http test failed (as the domain vanished). > > At 17:30 all my domains were invisible, so I just put the correct IP back > in all of them. Now I wait and maybe later tonight I'll find that my REST > API is working as I originally expected. > > Amazing eh?! -- *Greg K* > > On 7 August 2015 at 17:35, Bec C > wrote: > >> >> On Fri, Aug 7, 2015 at 5:19 PM, Greg Keogh > > wrote: >> >>> Does the https one work on its own (http one removed or disabled)? >>> >>> They are completely independent, in different sites and different app >>> pools, they only share the executable files folder (and I know the >>> permissions are okay). The https one times out under all experiments I've >>> run so far. I'm really surprised because REST style services and projects >>> are relatively simple compared to WCF services where I've previously had to >>> tweak the config file for https or http (which took hours of research!). I >>> expected it to just GO! -- *GK* >>> >> >> I'd just start with the https one alone and get that working just to >> ensure it has nothing to do with the sharing of files. If it doesn't work >> alone then https isn't configured correctly. Sorry not clear if you've >> already tried this. >> Also I think there is a "enableSSL" or similar somewhere in the project >> properties in case you've missed it. >> > >
Re: Web API and https timeout
OK FOLKS! Those of you who are sys admins don't laugh at what I just found, by accidentally noticing that all of my web sites where slowly vanishing throughout the afternoon... Around 11am this morning I finished migrating 6 of my domains from one provider to another. I set the DNS A records for all domains to point to my home server's IP address. However, I transposed two digits of the address and as a result, all domains slowly vanished as the records were propagated around the globe. That's certainly why my https test failed, then an hour later the http test failed (as the domain vanished). At 17:30 all my domains were invisible, so I just put the correct IP back in all of them. Now I wait and maybe later tonight I'll find that my REST API is working as I originally expected. Amazing eh?! -- *Greg K* On 7 August 2015 at 17:35, Bec C wrote: > > On Fri, Aug 7, 2015 at 5:19 PM, Greg Keogh wrote: > >> Does the https one work on its own (http one removed or disabled)? >>> >> >> They are completely independent, in different sites and different app >> pools, they only share the executable files folder (and I know the >> permissions are okay). The https one times out under all experiments I've >> run so far. I'm really surprised because REST style services and projects >> are relatively simple compared to WCF services where I've previously had to >> tweak the config file for https or http (which took hours of research!). I >> expected it to just GO! -- *GK* >> > > I'd just start with the https one alone and get that working just to > ensure it has nothing to do with the sharing of files. If it doesn't work > alone then https isn't configured correctly. Sorry not clear if you've > already tried this. > Also I think there is a "enableSSL" or similar somewhere in the project > properties in case you've missed it. >
Re: Web API and https timeout
On Fri, Aug 7, 2015 at 5:19 PM, Greg Keogh wrote: > Does the https one work on its own (http one removed or disabled)? >> > > They are completely independent, in different sites and different app > pools, they only share the executable files folder (and I know the > permissions are okay). The https one times out under all experiments I've > run so far. I'm really surprised because REST style services and projects > are relatively simple compared to WCF services where I've previously had to > tweak the config file for https or http (which took hours of research!). I > expected it to just GO! -- *GK* > I'd just start with the https one alone and get that working just to ensure it has nothing to do with the sharing of files. If it doesn't work alone then https isn't configured correctly. Sorry not clear if you've already tried this. Also I think there is a "enableSSL" or similar somewhere in the project properties in case you've missed it.
Re: Web API and https timeout
> > Does the https one work on its own (http one removed or disabled)? > They are completely independent, in different sites and different app pools, they only share the executable files folder (and I know the permissions are okay). The https one times out under all experiments I've run so far. I'm really surprised because REST style services and projects are relatively simple compared to WCF services where I've previously had to tweak the config file for https or http (which took hours of research!). I expected it to just GO! -- *GK*
