However, Visual Studio performance quickly degrades as the number of projects increases. Around the 40 project mark compilation becomes an obstacle to compiling and running the tests, so larger projects may benefit from consolidating test projects.
Steps to display the file path of the current open file (Excel 2007):
Right click on the ribbon
Choose "Customise quick access toolbar"
Select "All commands"
Then choose "Document Location"
Click "Add".. and it will appear on the right
http://www.technologyquestions.com/technology/microsoft-office/116356-office-2007-display-path-filename-menu-bar.html
To add the Document Location command to your Quick Access Toolbar(QAT):
- Click the More (or Customize) command at the end of the QAT and then click
More Commands.
- In Choose Commands From, select Commands Not In the Ribbon.
- Locate Document Location, select it, and then click Add to add it to your
QAT.
Prompt to open a Microsoft Office Word document as read-only
http://office.microsoft.com/en-us/accounting-help/prompt-to-open-a-microsoft-office-word-document-as-read-only-HP001173084.aspx
In a Word file, click the Microsoft Office Button , and then click Save As.
Click Tools, and then click General Options.
Select the Read-only recommended check box.
Click OK.
Click Save. If prompted, click Yes to update the existing file with the new read-only setting.
Normally it worked fine. But for particular data it has a huge response that was truncated.
The size returned in a few attempts in IE browser was 2196456, in Chrome slightly different 2195397.
After a search in google I found http://forums.asp.net/post/4948029.aspx, that has a number of suggestions.
For WCF service that will transfer large amount of data in operations, here are the configuration settings you need to check:
1) the maxReceivedMessageSize attribute of the certain <binding> element(in your case, that's the webHttpbinding)
#<webHttpBinding> http://msdn.microsoft.com/en-us/library/bb412176.aspx
2) The <readerQuotas> settings (under the <binding> elements) which has control over the maxarrayLength, maxStringLength ,etc...
#<readerQuotas> http://msdn.microsoft.com/en-us/library/ms731325.aspx
3) The DataContractSerializer behavior which has a MaxItemsInObjectGraph property. You can configure it via ServiceBehavior of your WCF service
#DataContractSerializer.MaxItemsInObjectGraph Property http://msdn.microsoft.com/en-us/library/system.runtime.serialization.datacontractserializer.maxitemsinobjectgraph.aspx
4) And if your WCF service is hosted in ASP.NET/IIS web application, you also need to enlarge the "maxRequestLength" attribute of the <httpRuntime> element (under <system.web> section).
#httpRuntime Element (ASP.NET Settings Schema) http://msdn.microsoft.com/en-us/library/e1f13641.aspx
After a few attempts my collegue found that our problem was caused by
https://nuget.org/packages/PostSharp.Patterns.Diagnostics/3.0.26 and
https://www.nuget.org/packages/PostSharp.Patterns.Diagnostics.NLog/
Install-Package PostSharp.Patterns.Diagnostics
Install-Package PostSharp.Patterns.Diagnostics.NLog
The install of
The installs haven't changed the content of PSPROJ files and I
had to manually update them.
1. Deleted old references to DLL and inserted
Task
<Data Name="XmlMulticast">
<Multicast>
<LogAttribute xmlns="clr-namespace:PostSharp.Toolkit.Diagnostics;assembly:PostSharp.Toolkit.Diagnostics" AttributeTargetAssemblies="Applications.MyApp" AttributeTargetTypes=" Applications.MyApp.MyCustomer" AttributeTargetMembers="*" OnExceptionLevel="Warning" OnExceptionOptions="IncludeParameterValue" />
</Project>
It was deployed to CI test environment, where we noticed delays and timeouts. I found that despite that only OnExceptionLevel and OnExceptionOptions were specified, the new LogAttribute generated verbose trace information, which caused severe performance hit.
For a long time I believed that PDB as a part of debugging information should not be included in production deployment. Recently my colleague suggested to copy them to simplify exception investigations.
The following SO discussion convinced us that it is a good idea ( at least for web sites).
http://stackoverflow.com/questions/933883/are-there-any-security-issues-leaving-the-pdb-debug-files-on-the-live-servers
These files will not be exposed to the public if kept in the right places (website\bin).
BTW, if you include PDBs with your deployments, you don't need to store them in a symbol server,
as it is suggested in http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/05/11/pdb-files-what-every-developer-must-know.aspx
To change setting in Visual Studio there is an option in the "Project Properties", "Build", "Advanced...".
Change "Debug Info:" to PDB-only.
The screenshots are available in the posthttp://callicode.com/Homeltpagegt/tabid/38/EntryId/24/How-to-disable-pdb-generation-in-Visual-Studio-2008.aspx
/optimize+ /debug:pdbonly (release configuration of visual studio)
2PC in the cloud is hard for all sorts of reasons. 2PC as implemented by DTC effectively depends on the coordinator and its log and connectivity to the coordinator to be very highly available. It also depends on all parties cooperating on a positive outcome in an expedient fashion. To that end, you need to run DTC in a failover cluster, because it’s the Achilles heel of the whole system and any transaction depends on DTC clearing it.
The bottom line is that Service Bus, specifically with its de-duplication features for sending and with its reliable delivery support using Peek-Lock (which we didn’t discuss in the thread, but see here and also here) is a great tool to compensate for the lack of coordinator support in the cloudThe Azure storage folks implement their clusters in a very particular way to provide highly-scalable, highly-available, and strongly consistent storage – and they are using a quorum based protocol (Paxos) rather than classic atomic TX protocol to reach consensus.
The Azure storage folks implement their clusters in a very particular way to provide highly-scalable, highly-available, and strongly consistent storage – and they are using a quorum based protocol (Paxos) rather than classic atomic TX protocol to reach consensus.
In the current release, only one top level messaging entity, such as a queue or topic can participate in a transaction, and the transaction cannot include any other transaction resource managers, making transactions spanning a messaging entity and a database not possible.
Has Windows Azure any kind of distributed transaction mechanism in order to include any remote object creation in an atomic transaction including other domain-specific operations?
call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86 tf shelve /replace /comment:"Current backup" CurrentBackupMT01 /nopromptpause
There is nothing wrong with static methods and they are easy to test (so long as they don't change any static data). For instance, think of a Maths library, which is good candidate for a static class with static methods Static methods which hold no state and cause no side effects should be easily unit testable. In fact, I consider such methods a "poor-man's" form of functional programming; you hand the method an object or value, and it returns an object or value. Nothing more. I don't see how such methods would negatively affect unit testing at all.
RSS ATOM