From here: https://blogs.technet.microsoft.com/enterprisemobility/2009/07/01/using-multiple-monitors-in-remote-desktop-session/
If your RDP's "Use all my monitors for the remote session" is disabled you can get around it as follows.
1. Create an RDP file with your specific connection.
2. Right click on the .rdp file and select Open with Notepad.
3. Add the following 2 lines to the bottom.
span monitors:i:1
use multimon:i:1
4. Save and then use!
Have a great day!
From here: http://superuser.com/questions/803943/how-to-disable-javascript-debugging-in-ie11
The options in VS for exceptions to determine if the debugger should break on an exception. Though VS will always break on an unhandled exception and a language break (debugger). The options do not stop the script debugger from being attached when you launch IE from VS.
The options in VS to enable or disable JIT debugging change just the just-in-time debug feature. Enabling JIT debug simply means that if a running application not launched by VS hits a break condition the user should be prompted if they want to attach VS to debug the application. This also don't change if script debugging is enabled when you launch IE from VS.
The options in Internet Explorer to disable script debugging only changes if IE should run with debugging enabled always. In IE11 with VS2013 this feature is never needed but is there to support older versions of VS.
The easiest way to get the behavior you want is to do:
1. Right click on a aspx/html file there is a ‘Browse with…’ item. This will bring up a dialog to configure your browser.
2. Click the Add button. Add something like:
Path: c:\Program Files (x86)\Internet Explorer\iexplore.exe
Friendly name: Internet Explorer (no debug)
3. Set that as your default
This basically launches IE outsie Visual Studio so that those annoying Javascript errors stop happening. You will still be able to debug your code though.
<style type="text/css">
tr:nth-child(odd) { background-color: #ecf1f2; padding: 4px;}
tr:nth-child(even) { background-color: #fff; padding: 4px;}
table { border-collapse: collapse; border-spacing: 0; }
</style>
From: https://msdn.microsoft.com/en-us/library/dd207045.aspx
-
On the design surface, click the row or column handle of the tablix data region to select it. The Grouping pane displays the row and column groups.
-
On the right side of the Grouping pane, click the down arrow, and then click Advanced Mode. The Row Groups pane displays the hierarchical static and dynamic members for the row groups hierarchy and the Column groups pane shows a similar display for the column groups hierarchy.
-
Click the static member that corresponds to the static member (row or column) that you want to remain visible while scrolling. The Properties pane displays the Tablix Member properties.
If you don’t see the Properties pane, click the View tab at the top of the Report Builder window and then click Properties.
-
In the Properties pane, set RepeatOnNewPage to True.
-
Set KeepWithGroup to After.
-
Repeat this for as many adjacent members as you want to repeat.
-
Preview the report.
Recently I had to link to 4 SQL Azure tables that are in a Access Web App and found a way to always connect even though MS Access does not save the UserName/Password in the connection string.
The SQL Azure connection string is as follows, however note that when you view the connection string in desgin mode you will not see the UID/PWD part.
ODBC;Driver={SQL Server Native Client 11.0}; Server=[Server Name].database.windows.net; Database=[Database Name];
Uid=[Database Name]_ExternalWriter; Pwd=[Password]; Encrypt=Yes
So in order to get around this issue, create a Passthrough Query to one of the Linked SQL Azure tables and save the Uid/Pwd with the connection string. Make it some thing like SELECT TOP 1 * From Access.[Table Name]. Save the query as something like qptSQLAzureStartUp. Then Add this to the StartUp form's OnOpen Event: Dim lngCount As Long and the next line as lngCount=DCount("*", "qptSQLAzureStartUp"). Then you'll find that your Linked SQL Azure tables will open.
Check this link too. This works for MVC 5 too: http://stackoverflow.com/questions/12433736/asp-net-mvc-4-allow-dashes-hypens-in-urls
Dashed urls are much more SEO friendly and easier to read. (More on my blog post)
NuGet Package: https://www.nuget.org/packages/LowercaseDashedRoute/
To install it, simply open the NuGet window in the Visual Studio by right clicking the Project and selecting NuGet Package Manager, and on the "Online" tab type "Lowercase Dashed Route", and it should pop up.
Alternatively, you can run this code in the Package Manager Console:
Install-Package LowercaseDashedRoute
After that you should open App_Start/RouteConfig.cs and comment out existing route.MapRoute(...) call and add this instead:
routes.Add(new LowercaseDashedRoute("{controller}/{action}/{id}",
new RouteValueDictionary(
new { controller = "Home", action = "Index", id = UrlParameter.Optional }),
new DashedRouteHandler()
)
);
That's it. All the urls are lowercase, dashed, and converted implicitly without you doing anything more.
Open Source Project Url: https://github.com/AtaS/lowercase-dashed-route
I ran into an issue today with my FTP PowerShell script not working. It was configured to use port 21 as it has for years. The FTP site is at my son's house and he just got a new modem when he changed his provide to Telus. I found out that Telus block port 21 so I changed it to port 22, however then ran into a PASV (passive mode) issue where it would not upload files. After several hours I figured out that I needed to set the internal router to allow ports 49152-65534 in and then also had to do the same in IIS under the FTP site as well as set the Exteranl IP Address of Firewall to the IP address of the modem/router.
I found help here if the like still works: http://stackoverflow.com/questions/21032577/how-use-passive-mode-in-ftpwebrequest-fix-pasv-error-in-net-3-5-define-port/21051211#21051211
Visual Studio 2010
If you don’t want the Output Window to show up every time you do a build, you can easily keep it from happening by going to Tools -> Options -> Projects and Solutions -> General and deselect the “Show Output window when build starts” option: