Hey everyone,
I ran into the following error while trying to install Sql Server Management Studio on Windows 8:
To fix it, all you need to do is run the exe with administrative privileges.
Hey everyone,
Just posting this in case anyone else runs into it. After unshelving, the following error kept popping up when I tried to open files using the solution explorer:
I’m still not sure what caused it, but restarting visual studio seems to have fixed it.
Hey everyone,
I was mucking around with xampp this morning and ran into the following issue with apache:
In order to fix this, you can just kill the process that is blocking the port. Unfortunately I had IIS on this and needed another solution. As always, stackoverflow had the answer:
– In the xampp control panel, click config (same line as apache) and open the httpd.conf file
– Search for listen 80 and change it to list 8080 (or an alternative free port)
– Save and close the file
– In the xampp control panel, click config (top right)
– Click service and port settings and change the main port (and ssl if necessary) to match your httpd.conf file
– Click save and restart apache (note you may also need to run as administrator)
Check out this link for more info: http://stackoverflow.com/a/25113205/522859
Hey everyone,
Just an error I came across while trying to use a new solution project:
The fix for this was simply to run the following command in the package manager console:
PM> Install-Package EntityFramework
Thanks to StackOverflow for the details: http://stackoverflow.com/a/18642452/522859
Hey everyone,
I ran into this error message while trying to debug a project today:
The workaround to this was actually pretty weird. Remove all of your breakpoints that appear before this exception and place one after it instead. That’s it!
A bit of a weird issue, but according to the StackOverflow post where I found the solution Microsoft are aware of it: http://stackoverflow.com/a/23529882/522859
Hey everyone,
I was following the guide provided via the startup.auth.cs link on how to add Google authentication to your app. The problem I hit was that the example types used weren’t available, specifically GoogleOAuth2AuthenticationOptions.
Thankfully the fix fix for this was pretty easy, simply update OWIN via NuGet:
– Right click on your project
– Go to Manage NuGet Packages
– Click on the updates drop down
– Search for OWIN
– Update all of the relevant options
Thanks to this Stackoverflow post for the solution: http://stackoverflow.com/a/23606431/522859
Hey everyone,
Just a quick post on something useful I came across today. In JavaScript you can access the stack trace via console using the following command (ctrl + shift + j):
console.trace()
In Chrome, this will let you navigate to each relevant call by clicking the line number in the console window. I’ve found it pretty useful for backtracking through jQuery exceptions.
For more info, check out this Stackoverflow post: http://stackoverflow.com/q/6715571/522859
Hey everyone,
In order to verify that a pay response is legitimate, PayPal provides a unique token for each request. This token can then be matched against payment confirmation requests to ensure that they aren’t being spoofed. The problem I ran into was that even the legitimate IPNs I received did not contain a pay key.
It turns out that PayPal sends two different types of IPNs. The first is configured when making the API request. The second is configured in the PayPal account under “My Account > Profile > Instant PayPal Notification”.
The first type, includes the required PayKey, the second does not. Simply configure your profile details to point to another url and everything should work!
For more info, check out this stackoverflow post: http://stackoverflow.com/a/12031887/522859
Hey everyone,
I started receiving this error after I added the following elements to my Web.config file:
The problem turned out to be that the custom errors entry actually belongs under system.web. All you actually need to add it the <customErrors mode=”Off”/> part – just make sure it’s under system.web.
Hey everyone,
I’ve just upgraded to Visual Studio 2013 and ran into the following while trying to run IIS express:
The solution ended up being pretty obvious, I didn’t have permission. Run it with administrative privileges and the error goes away.
What I Broke - Programming and Web Development 