By default the sproc is disabled, something to do with a security concern.
To enable the procedure run the following in a query window: EXEC sp_configure 'xp_cmdshell', 1
If that doesn’t work, and it didn’t for me – I’m running SQL Server 2008 R2. Then run the following commands: EXEC sp_configure 'show advanced options', 1;
EXEC sp_configure 'xp_cmdshell',1
You can then run something like:
EXEC xp_cmdshell 'iisreset'
If you see this tooltip when examining your break points “The break point will not currently be hit. No symbols have been loaded for this document” then you’ve found the same issue that has been driving me mad for a few hours, it must mean you’re new to debugging web sites as well!
Simple solution (sic) is to right-click on your solution file and select “Properties” and then under Common Properties->Startup Project select the “Multiple startup projects” and set whatever action you require against the project(s) you want to debug.
Simples! Applies to Visual Studio 2010 onwards, and not just VS2013 as I at first thought.
This may also apply to Windows 8 and Windows 8.1, I haven’t looked at them.
Started running an azure virtual machine, very, recently to do some Visual Studio 2013 work/testing/playing and all going well, really impressive to be honest.
Hit an issue with trying to figure out how local and temporary storage works on the VM and so went to fire up Internet Explorer when I got a blue bar across the centre of the screen with the message “This app can’t open” and some associated text that “Internet Explorer can’t be opened using the Built-in Administrator account. Sign in with a different account and try again.” – WTF?
The VM was created with only one account out of the box, it was a pre-rolled distribution from Microsoft that included the OS, VS 2013 and SQL Server. What do you mean I can’t run a browser?
Seems to be an oversight on the distribution, IMHO which isn’t worth much to MS I’d imagine.
The solution to is fire up the Local Security Policy console (Windows key & R, then enter “secpol.msc”) and change the following value to “Enabled” and reboot the VM, the path to the value is “Local Policies->Security Options->User Account Control: Admin Approval Mode for the Built-in Administrator“.
To find out what your current MTU is open an admistrative command prompt and then type netsh interface ipv4 show subinterfaces
Then start pinging a site until you get the “Packet needs to be fragmented but DF set”, drop down until you no longer recieve this. ping somesite.com -f -l 1464
Add the 28 byte overhead to the maximum value you used above, this gives you your new MTU size. In my case 1464 + 28 = 1492, the normal for a PPoE connection.
Then set this value in your router and also in Windows. To set the value in Windows 7 use: netsh interface ipv4 set subinterface "Local Area Connection" mtu=1492 store=persistent
You should probably do some speed tests before and after just to see if that has improved.
If using SQL SSMS 17+ then you need to make sure that the Tools>Options>Query Results>SQL Server>Results to Grid>Retain CR/LF on copy or save is checked.
Otherwise carriage returns are lost.
After checking the option you need to restart SSMS.
Rather than always adding the reference directory to the csproj file have a read of this Microsoft article that talks about changing registry settings, either for the current user or for the entire machine.