Hot answers tagged .net
Based on the info in the MySQL Documentation you should do the following: Find out what the highest number of simultaneous connections mysqld has had using Connections, Threads_created, and Max_used_connections, SHOW GLOBAL STATUS LIKE 'Connections'; SHOW GLOBAL STATUS LIKE 'Threads_created'; SHOW GLOBAL STATUS LIKE 'Max_used_connections'; Try ...
It's not necessary to install Visual Studio 2012. Just copy the files in the following folder from a computer with VS2012 installed to your build server and it should work: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\WebApplications\
I had a similar problem. This thread http://stackoverflow.com/questions/2374957/asp-net-mvc-on-iis-7-5 solved it for me. Basically try adding this to your web.config: <system.webServer> <modules runAllManagedModulesForAllRequests="true"/> </system.webServer> If that work you can try removing it and install this hotfix instead: ...
Windows and linux have two different page/swap strategies. Linux Linux wants to avoid using swap space at all, and waits until the last possible moment. If you see a large amount of swap in linux, your system likely is or was in trouble. This strategy is good for minimizing overall disk i/o, which is the slowest part of your system, but weaker for systems ...
Backwards compatible is a bad term to use. .NET 1.0, 1.1, and 2.0 are their own frameworks that have no compatibility between each other. .NET 3.0 and 3.5 are super sets of the 2.0 framework, using the .NET 2.0 base framework, with additional dll's to provide additional features (3.0 included things like WCF and WWF, 3.5 had things like LINQ). In terms of ...
I think the answer will be No. Anything else would be a major hack, .NET install updates all sorts of things in the system, and its loader assumes those things are in place (e.g. GAC exists, location of compilers, IIS/IE/... integration).
Yes, you're good to go. .NET framework versions are designed to install side-by-side. The other versions of the framework will happily continue on with their lives. One thing I will add is that sometimes newer versions of the framework will patch older versions if necessary.
It makes IIS point to different root level config files for .NET. These root level files reside within the framework installation folders in %systemroot%\Microsoft.NET\Framework\<version>\CONFIG IIS looks for config files for itself in %systemroot%\system32\inetsrv\config\applicationHost.config and for .NET in ...
As long as the two applications are running in a different AppPool, it's like having two separate servers. No problems.
There is no chance, in my own humble opinion, that .NET skills will be bad for you. Quite the contrary. If you have familiarity with the .NET framework then you're much better equipped to utilize Powershell to its fullest extent which will do nothing but help you with sysadmin related automation tasks. The pointy haired boss should realize that you can ...
You can script everything for Exchange in PowerShell, assuming you're on 2010. You can script and awful lot in 2007 as well. Here is a good resource for Exchange 2010 scripting. Also, I know that "Google it" is not an acceptable answer here, which is why I provided you with a real answer, but there are literally hundreds of useful results when googling ...
The benefit of using C# 4.0? Developer Productivity. End users wouldn't be able to tell the difference between any of the other versions of the framework. So it's unlikely they would with this one. BUT there are a heap of benefits for developers: New Features in C# 4.0
This looks like the right link to me.
SQL Compact Edition: http://www.microsoft.com/sqlserver/2005/en/us/compact.aspx
Windows (and Linux & other Unix-a-like OSs) will move pages that have not been used for some time to disk to make room for buffers and cache to speed up active I/O activity. Also applications will often allocate more memory than they are immediately going to use - this may encourage the Kernel to page some things that have not recently been touched in ...
You will need to use a server control panel that is tailored to multi-tenancy and web hosting. There is no native way that Windows can perform this. It's not an easy task or something that can be done on your own without heavy investments in time, development and money. There are a few open-source tools that offer this kind of functionality, however most ...
If you add the MVC DLLs to you bin directory it will host happily on any up to date ASP.Net host. Personally I use an Discount ASP.Net and am very happy with them.
I just tried the installer on Windows 7 RC to see what happend, and got the following message (which happens to have the solution to your problem :) "You must use 'Turn Windows features on or off' in the Control Panel to install or configure Microsoft .NET Framework 3.5 SP1." Sure enough, there it is. Enable it by clicking Start --> Control Panel --> ...
Yes, if you set the project properties to use 32-bit (x86 I think) explicitly it will always run in that mode. We had that issue when using the SQLite ADO.Net provider (it was looking for the 32-bit version only, which couldn't load when run on a x64 system). You can use corflags to set the 32-bit bit (ha ha) flag on the executable. Here is an example. In ...
This isn't a dumb question at all. it's actually a good question. My information may be out of date, but in earlier versions of the home Operating Systems (Win98 - WinXP) the version of IIS (or Personal Web Server on the older OS's) that ships with the operating system is limited to fewer connections (10 the last I knew), so that alone rules out hosting a ...
You can't copy AD users. You can move them from one place to another, or you can create new users based on existing ones... but in the latter case, you have to supply new user names, passwords and a few other things; it's not as simple as a "copy & paste" operation. Users are security principals, they must be unique in a given domain; you can't have ...
By default, nmap only scans for "common" ports (the 1000 most common ports per protocol I believe). Since 789 is not a common port it isn't found. If you do nmap -A -vv -p- ip it should scan ports 1-65535. Here is the nmap documentation that tells what ports are scanned by default: http://nmap.org/book/man-port-specification.html
Windows Server 2003 already ships with Framework 1.1 so you don't really need to worry about installing that other than applying patches via Windows Update. Framework 1.1 is fairly old and from experience pretty much all 1.1 code will run on 2.0 unmodified. Framework 2.0 is a major release, it's still fairly popular so I'd go ahead and install that. This ...
Our internal developers always want the latest .Net framework, and we typically try to accommodate them. We're in the process of rolling out .Net 4 to our computers which are a mix of Windows XP and Windows 7. We're not seeing any issue. Cost: If you need to test each and every system with all software installed, I would envision a large cost to ...
The "best-practice" is generally not to run software that requires you to use a vulnerable framework (or, say an older version of Java), but that is not always an acceptable answer, unfortunately. For most businesses (those that aren't technology or IT-based, at least), IT serves business needs, and not the other way around, so you don't always get to use ...
Both Vista and Server 2008 come with .Net 3.0. This includes the .NET 2.0 runtime (CLR) as well as the framework and library additions of 3.0 (WF, WCF, WPF).
XP didn't ship with any .NET, SP1 and 2 had v1.0 as an option, SP3 installed v1.0+bugfixes by default. Server 2003 shipped with v1.1, Vista and Server 2008 with v3.0 and finally W7 and 2008R2 with v3.5. All can run 1.0, 1.1, 2.0, 3.0, 3.5 & 4.0b1 if installed/updated.
For enumerations you don't have to specify the whole type name. For example: You can do this: New-Object System.DirectoryServices.ActiveDirectory.DirectoryContext([System.DirectoryServices.ActiveDirectory.DirectoryContextType]::Domain) or the much more simple version: New-Object System.DirectoryServices.ActiveDirectory.DirectoryContext('Domain') You ...
<%windir%>Microsoft.NET/Framework/v3.0/Windows Communication Foundation/ServiceModelReg.exe -i ...then <%windir%>Microsoft.NET/Framework/v2.0.50727/aspnet_regiis -i -enable This mapped the proper isapi dll's to the *svc extension, among other things. Bless Microsoft...
Only top voted, non community-wiki answers of a minimum length are eligible