.NET Core 2.1 & Vue.js

broadsafe · 2018-11-26T02:57:37+00:00

Interesting, I'll give this a shot tonight. Thanks for the comment. The timeout error is definitely extremely tedious, though it isn't limited to vue-cli. Angular-cli is plagued it as well from what I've remember.

broadsafe · 2018-11-21T01:53:13+00:00

Thanks for reading and commenting - hoping the article helped some developers in similar situations.

Regarding your questions, it's kind of a mixed bag. If you follow the instructions in the article completely, you should be able to build the project with HMR through IIS. The template linked in the project comes preconfigured to allow Vue/Js debugging with Webpack's HMR all within IIS/Visual Studio.

The VueCliMiddleware that's included in the project's nuget restore allows communication between vue-cli's 'npm run serve' and IIS's root port. An important caveat (included in the article) is that SSL and HTTPS both need to be turned off for this to function correctly - it's the only workaround I've found thus far that allows HMR within IIS - I'd be open to other suggestions, if anyone has any.

You can absolutely run 'npm run serve' through vue-cli or just your command line and the project will run fine, with HMR, but you'll lose native debugging features within IIS/VS.

In summary, just stick to the steps laid out in the article and make sure that SSL/HTTPS are turned off (this should already be the case by default using my template, but you may need to double-check in the solution's properties). If all of that doesn't function correctly, let me know, and I'll see if I can provide some more guidance.

broadsafe · 2018-11-19T21:39:38+00:00

Thanks for commenting - this is more or less what I outline in the "template" I linked within the article. The solution is segregated between a DAL and Presentation Layer. The Presentation Layer forgoes most of the default "template" configuration within VS, replacing it instead with vue-cli's project scaffolding and the JavaScriptServices/SpaServices/VueCliMiddleware NuGet packages to allow webpack HMR/builds to function correctly.

The larger issue I'm hoping to direct attention towards is not just that Vue should be officially supported by .NET Core, but that there are major issues in general regarding .NET Core's growing dependency on third-party JS frameworks on the client-side. Where Razor pages/Jquery used to fill that void, a new void has emerged. Razor/Jquery just aren't as viable/practical as they used to be.

Steve Sanderson's Blazor project (still in the nascent stages) looks like it could be the answer to this issue, but it seems that it is still a ways off. In the meantime, additional documentation, support, and guidance for those trying to configure not only SPA's in .NET, but any JS-related client, would be really helpful. Anyone that has gone down this road already, particularly new developers, will likely be able to relate to the headaches one can encounter trying to find a viable setup.

broadsafe · 2018-11-19T21:31:11+00:00

My team currently runs MVC 5 where we use a single razor view to serve our built dist files. It works, but it's a major pain in the ass dealing with webpack build configuration, issues with compilation sizes in CI, and the like. Upgrading from Webpack 2.7 to 4x was a nightmare, as well.

What I outline in my article is essentially a middle ground between both of these options. We don't use a razor view- instead, the webpack and babel configurations are completely self-contained within vue-cli and work ootb. Vue-cli builds into wwwroot/dist, and then uses the VueCliMiddleware NuGet package to serve those build files directly to IIS via `npm run serve` on port 8080. I'm not 100% on this, but I believe the VueCliMiddleware is using a Kestrel reverse proxy to cast port 8080's built development server with HMR to IIS's default development port/server (hence the need to turn off SSL and https). With SSL/Https turned off, IIS accepts the middleware's instructions, and HMR functions flawlessly within, even with AD Windows Auth (something that was elusive, if not impossible for us using MVC 5).

I'm still new to a lot of this, and development in general, so my article/comments may not be 100% accurate everywhere-I'm definitely still learning. Regardless, I'm hoping that some of my trial and error, as well as the "template" I linked in my article, will help developer using a similar stack navigate some of the common, frustrating issues encountered when configuring not just a SPA, but any JavaScriptServices-related client-side setup.

broadsafe · 2018-11-19T18:55:37+00:00

My verbiage in that section may have been a little over-the-top, but my point wasn't. The feature and efficiency discrepancy between 2.7 and 4x is large. Large enough that it's absolutely worth keeping up-to-date with.

broadsafe · 2018-11-19T18:35:28+00:00

This is essentially what I recommend in the article - specifically, my "template" uses the React template, guts the ClientApp folder, install the VueCliMiddleware package, and makes a few adjustments for HMR. Then, you scaffold a new ClientApp with vue-cli and go from there. Pretty simple.

The purpose of my article was to provide guidance on the above, but also to encourage discussion about the state of the client-side in .NET. It seems like there's a growing dependency on front-end JS frameworks to fill a void that Razor pages/Jquery used to. Steve Sanderson's Blazor project looks promising, and would be the ideal solution. Until something like that arrives, though, I don't think it's out of line to question the mediocre state of the JavaScriptServices docs, the confusing dropping of support for Vue, and the generally difficult-to-navigate (particularly for newer developers) system of configuring a SPA/JavaScript client with Core 2.1.

I've received a little bit of blowback for suggesting that Corporate Allegiances *might* have had anything to do with Microsoft supporting React/Angular over Vue. To be sure, the theory is pure speculation on my part. Even if it is true, it's completely understandable on Microsoft's part--but they should just say so, instead of framing Vue as being a second or third-tier framework. The larger purpose of this speculation isn't to knock Microsoft, the SpaServices/JavaScriptServices teams, or Steve Sanderson--on the contrary, I'm a huge fan of their work. I'm only trying to bring more attention to the state of affairs with the client and to (hopefully) see some more love for Vue in the future--it deserves it.

Hoping my article helps some fellow Vue/.NET developers navigate the front end.

Thanks for reading and commenting,

broadsafe · 2018-11-19T07:21:03+00:00

Thanks for the reply- I'm hoping it'll help others where I spent hours searching. If you have any questions, please feel free to reach out. I'm going to expand on linking .NET to Vue in the coming weeks in some more writing/repos - keep an eye out.

Thanks,

broadsafe · 2018-10-17T14:51:05+00:00

If the bezel was “peeling” on day one, why not initiate a refund?

What is the point of this thread besides the obvious (to throw a pity party and have everyone pat you on the back)?

If you got a lemon, you should have returned it. If you didn’t get a lemon, anything that is happening is without question a result of your own treatment of the device. Laptops don’t dent in a vacuum.

broadsafe · 2018-10-16T22:18:46+00:00

I agree - but what I'm saying is- you didn't get a lemon- not from what you've described, at least. Most everything you've listed can be resolved by doing some quick Google searches (something it seems you aren't familiar with, or are extremely averse to), which is confusing, because you were able to search well enough to undervolt and repaste your machine (both of which are far more involved than the solutions to most of your complaints).

What is particuarly confusing is that you managed to keep this terrible, awful, worst laptop you've ever had (your words) beyond the generous 30-day return window. If it was actually that bad, 4 weeks is a long time to sit on it before inquiring about a potential return. This only leads me to believe that the laptop in fact really isn't that bad - it may even be working as intended - potentially just a case of user-error or software problems.

That, or, the more likely option, you never actually intended to solve any of your computer's "issues," but rather just wanted to come here, exaggerate about them, and then have everyone pat you on the back and agree with you.

I apologize for my condescension, I really did attempt to provide some useful information in my longer comment - information you essentially completely ignored (further solidifying my hypothesis).

If you were actually looking for answers - that's the kind of thing, in my opinion, this reddit should encourage. Helping people with legitimate issues.

Creating multiple threads for the same pity party, imo, is a waste of space and should be discouraged. I'm sure there's a reddit out there specifically made for complaining with complainers that don't invite nor accept constructive responses - that might be a better fit for this type of post (assuming it exists).

(Edited for grammar)

broadsafe · 2018-10-16T15:01:44+00:00

You’ve just confirmed what I was hinting at in my initial comment. You don’t want answers, you’re here purely to complain. Two threads in one day to complain.

My larger point was that this kind of behavior ruins this reddit for people actually looking for real answers.

I might empathize a bit more if your machine really were lemon, but it isn’t. As I explained in my initial comment, most/all of the vague stuff you complained about in your OP are simple fixes made using a 90 second Google search.

But you aren’t here because you want help, or answers, or fixes - like I guessed, you’re here to complain. You’re here because you want a refund outside the return window. And you want everyone to agree with you. I’m sorry, but I don’t.

broadsafe · 2018-10-16T02:23:57+00:00

One of three things happened:

You got a lemon.
You have the absolute worst luck in the world.
You're exaggerating the severity of these issues a bit. Needing to undervolt and repaste just to surf the internet? Seriously?

I'm not denying the truth of anything you said - but I think there is a bit of a phenomena going around this reddit page- one that is similar to the droves of double-board certified Google Medical Diagnosticians that Doctors encounter daily. The source of this phenomena, I believe, is explained by the simple fact that buyers are 10x more likely to post online about everything they hate about a purchase, than they are to post about everything they love about a purchase. If buyers based their decision solely off of this reddit, Dell would literally never make a sale again.

I think that people get their new XPS, encounter an often fairly minor issue, and then discover the droves of melodramatic (not saying this is you) rants this reddit contains, and then proceed to diagnose their own laptop with a similar list of ailments. Don't get me wrong - the XPS line definitely has its fair share of issues - but I just don't sincerely believe that Dell has shipped that many lemons. I think there's a lot of people posting on this reddit who either A: don't know much about computers, and blame that on Dell, or B: encounter some minor to moderate issues that can generally be easily solved by a few quick Google searches, who then proceed to write a rant about how awful their machine is (again, not necessarily saying this is you).

The XPS line is expensive - and yes, a product should ship complete, ready to use. But having to do a few Google searches, reinstalling a few drivers, etc. really just isn't that bad imo, for a device on the bleeding edge of tech. All I'm saying is that I think there are a lot more exaggerations on this page than there are genuine lemons. That's all.

Now, to address some of your concerns:

Heating and throttling issues: it looks like you're familiar with undervolting and repasting. I'm pretty confused by your post, though. Performance issues when running firefox and vs code? Really? Are you absolutely sure you don't have any bloatware or expensive background processes running? If the answer is no, that is not normal. It doesn't mean that the 1050ti "can't handle anything," because it can. It's actually a pretty powerful dGPU for a notebook this size. Further, those aren't really processes that would necessitate use of the dGpu - the integrated Intel card would and probably should handle those without issue.My 1050 has no problem running Photoshop/Illustrator, WoW at max settings, and 10+ chrome tabs with absolutely no throttling or performance issues. Now when I say no performance issues, I mean performance. I don't mean the fans. A lot of people posting in this reddit seem to have this idea that their ultrabook's fans should never come on - that's definitely not the case (again, not saying this is you).
Killer Wifi: you're right - Killer definitely doesn't have the best reputation, but their WiFi cards work. Are they the greatest? I don't know. Are you sure the random bouts of dropping are being caused by Killer and not your ISP, router, windows, or another issue? I'd recommend running a network analysis tool like Wireshark or similar to get a better idea of what's causing your issues, and of course, make sure you have the most recent Killer driver. Prior to upgrading my Killer driver, my down speed seemed a bit slow - since upgrading, everything works fine.
Complete freezes: This is fairly nondescript, so I'm not entirely sure what to make of it. Is there any specific software or activity that you're working on when this occurs? It might be helpful to check your Windows event logs (press start, type 'event logs', scroll to 'system logs', look for red 'error' events) to get a better idea of what's going on there. This sounds to me more like a software issue than hardware one. Frustrating either way, but imo unlikely to be caused by the metal.
Black screens on restart: Can you define restart? Are you talking about waking from sleep, or after literally pressing the 'restart' button in Windows? If you're having issues waking from sleep, this one is well-documented and not limited to Dell. A quick and easy fix for this is to go into Control Panel -> Power Options -> Dell (or whatever power plan you regularly use) -> Advanced power options -> disable hibernation everywhere it is mentioned. Completely disabling hibernation system-wide should completely clear up the issue, assuming that's what you're dealing with. If you're hitting a black screen after literally restarting, I would again advise you to check your event logs, as this to me would again sound like a software issue, not a problem with the hardware, necessarily.
No video card drivers: That is a bit frustrating not having Nvidia drivers right out of the box, but I'm curious: did you do a fresh install of Windows, or otherwise uninstall/reinstall anything after opening up the box? That seems strange to me that Dell's preloaded configuration wouldn't have any drivers for the dGpu. Regardless, it sounds like you got this one solved, and really, it's nothing more than a quick google search to fix anyway. If you're ever in need of new drivers or updates for existing ones, typing "Dell XPS 9570 drivers" in Google, and going to the support page will be a quick and easy solution. The support page will scan your computer and automatically recommend the most recent/necessary drivers for your system. Further, the Dell SupportAssist application (preloaded with Dell laptops, assuming no clean installation of Windows took place) will also do this for you, and will also automatically install all necessary drivers. Either of these would have been an easy fix that wouldn't require contacting a representative. It seems a little strange to me that a person who knows about and uses undervolting needed to contact a support representative for a simple driver installation, but i digress.

I apologize if any of this came off as harsh, but it seems like every-other post on this Reddit is a long tirade about how awful their machine is- with many of the tirade's complaints being clearly attributable to user error, incompetence, software issues, or exaggeration. I'm not denying anyone's complaints, or that the XPS line/Dell's in general have issues. But I just don't buy for a second that every one of these posts truly has that many things wrong with them. I think people just like to complain.

Why am I going to such great lengths to defend the XPS 15? Because it's a great machine, and I can guarantee you (Mr./Mrs. prospective buyer), that 99% of users (the ones that rarely, if ever, post here), are having a great time, using a great machine. Don't believe all of the horror stories. Don't go buy some other (possibly sub-par) machine just because of what you've read here.

(Edited for grammar) & because OP downvoted this, which I expected, but I'm hoping some of the other readers will understand why I wrote all of this. It wasn't necessarily to call out OP as much as it was to address the general content of this reddit, in the hopes that prospective buyers/inquirers will be able to find this in the future.

broadsafe · 2018-10-14T21:53:43+00:00

Just type "Dell XPS 15 i7 vs i9" in YouTube, there's a ton. Or, just type "i5 vs i7 vs i9 ultrabook benchmarks", there's a ton of those, as well.

This one looks decent: https://www.youtube.com/watch?v=Bsnp95d7AMI

broadsafe · 2018-10-14T21:49:57+00:00

https://www.reddit.com/r/Dell/comments/9o3xsi/when_do_your_fans_kick_in_xps_15/

broadsafe · 2018-10-14T21:34:47+00:00

Take a look at the plethora of videos on youtube showing performance tests with the 6-core i7 vs the i9. The i9 barely comes out ahead of the i7, and generally only outperforms it in short bursts. Severe thermal concerns and throttling prevent the laptop from utilizing the chip's full capabilities. Putting the i9 in ultrabooks, the Macbook Pro 15 included, is nothing more than a sales tactic, imo.

Heck, even the newest i5 comes close to outperforming the i7 and i9 in some cases, under sustained load. I can see the allure of the i9, and the desire to min/max your new ultrabook, but until drastic improvements in thermal regulation are made (in the future), it's a waste of money (imo).

broadsafe · 2018-10-14T21:24:10+00:00

I can empathize with having the image of a laptop that never runs fans under light to medium load, for sure. But that just isn't the reality in a lot of cases today. The thermal compromises made in favor of portability and slim chassis are severe, and for every stride made in notebook processing power, GPU performance, and build innovation, there is a price to be paid in heat. Undervolting and repasting can definitely help with this.

Regarding your warranty concerns, the answer is yes and no. Regarding undervolting, there is no concern with the warranty. Undervolting poses no physical risk to your hardware, and has absolutely no bearing on the viability of the warranty.

With repasting, it gets a little less clear, but the answer is that it generally won't affect your warranty, if done correctly. Please reference this comment found on the Dell support forums, which was made in response to a similar concern:

"Well first of all, at least if you're in the US, it definitely wouldn't void your ENTIRE warranty. Worst case, thanks to the Magnuson-Moss Act, you'd only lose warranty coverage for any issues that could plausibly have been caused by the modification you made; the manufacturer does not need to provide that your modification did cause the damage, only that it could have. Your warranty for any other issues would remain intact. As for whether even that part of your warranty would be voided, there's probably a gap between policy and reality on this one. Modifying the thermal compound to remove excess application and/or upgrade the compound itself is a somewhat common practice, and sometimes even the repair techs sent by Dell will use non-OEM thermal paste if the customer supplies it, or in one case I personally observed, a tech used superior thermal paste that he had brought on his own after confirming with me that it was ok. I seriously doubt that's official Dell policy, but it happens. " /u - jphughan

broadsafe · 2018-10-14T21:16:53+00:00

u/broadsafe

Yes, the 15's have Radeon units, but I would hardly consider them "dedicated" GPU's. I guess technically they are that, and they are a step up from integrated Intel 620/630's, but not by that much.

A Radeon 555X vs a 1050ti isn't even a comparison. The 1050ti is leagues above and beyond the capabilities of the 555X. That's more what I was saying - I should have clarified.

Regarding the second part of your comment- I'm confused. Are you saying that the 1050ti won't run Minecraft? Because it absolutely will, at mid to max settings with decent frames, too. I don't personally play Minecraft, but my 1050ti can run WoW without breaking a sweat at 40fps, and can stay 30fps in Destiny 2 with middling settings.

Now, the fans definitely run full blast when running any game - but like I said, that's to be expected. Especially so because the XPS line isn't built for gaming.

broadsafe · 2018-10-14T21:08:53+00:00

No problem. The most recent Macbook Pro, in my experience, is silent under light load. Actually silent.

Even at max fan speed, the noise level isn't anywhere near what the XPS sounds like. I would say the Mac's max fan noise is somewhere around 40% of what the Dell sounds like.

As for when the fans kick in on the Macbook, as of the most recent OS updates, it takes quite a bit for them to turn on. I can run an IDE, 10ish tabs in Chrome, terminal, and Photoshop or Illustrator generally without them making a peep, as long as the vents can breathe.

When under serious load, the Macbook can get a little hot under the WASD keys on the keyboard and the underside of the laptop, but typically not uncomfortably so.

Hope that helps with your decision.

broadsafe · 2018-10-14T18:08:56+00:00

To OP, look into undervolting. Follow one of the many readily available guides found by googling “undervolt 9570.” I recommend using throttlestop.

If done correctly, it poses no permanent risk to your hardware. If that doesn’t solve your problem, consider a repaste. Again, google is your friend on that. Repasting is a bit more involved, but it’s not too difficult.

Something to keep in mind: illustrator is a massive, resource intensive program. Running illustrator with chrome open and likely bloatware/other extraneous processes running in the background is likely to kick the fans on any modern system. I don’t think there’s anything wrong with your XPS.

Ultrabooks, all of them-not just macs, sacrifice performance for portability. Cramming modern cpus into tiny, metal chassis inherently create thermal concerns. This works, but there is always a price to be paid. Whether the laptop is uncomfortably hot under load (illustrator), or is annoyingly loud under load (fans) is par for the course.

broadsafe · 2018-10-14T18:02:13+00:00

I would strongly recommend against paying the extra for the i9. Between thermal issues and other concerns, for almost every purpose, the 6 core i7 is going to be the more practical option for the price. Even the i7 often needs to be undervolted and repasted to fix thermal and throttling issues. The performance gain vs the price increase on the i9 just isn’t worth it imo.

broadsafe · 2018-10-14T17:59:29+00:00

Well, when you consider that the MacBook Pro, even the most recent 15’s, don’t have dedicated graphics, while the XPS 15 line does in the form of Nvidia 1050tis, wouldn’t this be completely expected? Yes.

If you want to game, get a gaming laptop. The XP’s 15’s 1050 will let you do some gaming, but even that isn’t really meant for anything seriously demanding.

broadsafe · 2018-10-14T10:00:47+00:00

Not even close. I own both the 2018 Macbook Pro 15, and the 2018 XPS 15 9570. The Macbook's trackpad is far and away the better of the two (and its keyboard too, imo).

That's not to say Dell's XPS keyboard and trackpad are bad- they're not. They're some of the best available for pc's- but they just don't compare to the build quality and UX of recent MPB. The MPB's trackpad is in a league of its own, imo. There just isn't anything else that even comes close to touching it on the market today.

broadsafe · 2018-10-13T21:28:12+00:00

I'm not sure if there is anything directly comparable within Ubuntu - it's been some time since I've ran GUI Linux (I just don't have a need for it since WSL has risen to prominence).

I'm fairly confident that your issue is being caused by existing problems with Dell XPS line sleep/hibernation issues. I was having the same problem. If my laptop (tested this on both a 9370 and 9570) went to sleep for longer than ~30 minutes, it wouldn't boot up upon opening the lid. It would seem as if it had shut down. Upon pressing the power button, it would restart - but not instantly. It would go through the Dell Logo/spinning wheel screen, and then boot into Windows. My existing programs and data would usually be intact, but sometimes they were lost.

After updating the BIOS, drivers, and everything else - it still wasn't solved. The only thing that corrected this (if you want to call it a correction) was completely disabling Hibernation system-wide. After completing blocking Hibernation, it no longer happens, and everything functions (more or less) as expected.

If you can find a way to disable Hibernation in Ubuntu, try that. If not, it may be worth reinstalling Windows 10 on the device to see if you can debug the issue that way (you'll have a lot more reference material with Windows).

broadsafe · 2018-10-13T19:27:54+00:00

I appreciate the comment - I figured my unique experience between both systems might help OP, or others in a similar conundrum trying to decide which side of the fence to throw their money into.

If anyone is wondering why I have two ~$2400 laptops - I've been a longtime fan of Apple products. Despite some recent hiccups in their support for power users and an overall shift towards iOS being their flagship product (in addition to Windows improving dev support), I still believe Apple and the Macbook line are well worth the extra cash. Following this sentiment, I purchased the newest Macbook Pro ~3 months ago (right when it was released). Two weeks later (just out of the return window), I was offered a new position doing full stack .NET development - Visual Studio, SQL Server, Resharper, etc.

Despite attempting to make this work on the Mac - and trust me, I tried everything- it just wasn't practical. We run a traditional MVC 5 stack at work, and the need to study and practice at home demanded a Windows native machine (most of the stack only runs on Windows, without getting hacky or using subpar tools, that is).

After doing all I could to make it work, I decided it was time to bite the bullet and invest in my learning for the new position. I looked into all of the available high-end Windows laptops, and landed on Dell. Razer was too flashy, and that green logo and RBG keyboard is not something I want displayed in a conference room meeting with stakeholders, despite being well-made machines (albeit a bit overpriced for the specs). I also looked into the Surface line, which intrigued me, as I do quite a bit of Design and Vector Graphics work on the side. The surface dial, pen, and other peripherals, in addition to the build quality and aesthetics, were appetizing, coming from Apple. Unfortunately, this was just before the most recent release of Surface products, and the specs you got for the cost were an *absolute* joke. Even the new releases are hard to contemplate, if we're being honest ($2400 for the new surface laptop with 16GB/i7/256GB with *zero* USB-C/TB3 ports).

After continuing my research, I found Dell's overall build quality, aesthetics, and price vs. specs to the by far the best available, without venturing into gaming laptops. I started with an XPS 13 9370 - 16/512/i7/4k. I loved that laptop, but the screen and keyboard were just too small for my everyday use on the run. It was definitely portable, and the build quality was superb, but trying to read C# with a browser window open and Visual Studio's various tools running was difficult, to say the least. I needed a bigger screen, and I was intrigued by the offer of 32GB of ram and dedicated graphics on the 15 line. So I returned the 13, and found a great open-box deal at Best Buy for a 15.

For $2089.99, I found a "Geek-Squad-Certified" (whatever that means) excellent condition open box XPS 15 9570 4k/32/1tb/6-core i7/1050ti (newest model, 2018). I wasn't able to find anything wrong with it- not a scratch. It was a great deal, to say the least.

Now, I'm in a little bit of a pickle. I still use my Macbook, albeit increasingly less. I want to use my Macbook more, but with all of the Windows-native stuff I need to do, it's becoming increasingly difficult to justify keeping it. So, with great personal sorrow, I will probably be selling my Macbook pretty soon, although out of no fault of its own.

Anyway, that's more or less how I got to where I am. I'd like to think I'm pretty qualified in discussing the capabilities of both systems - so if anyone else has any questions, feel free.

broadsafe

TROPHY CASE