'==' Operators are overloaded, not overridden, which means that unless the compiler knows to call the more specific version, it'll just call the object version
Angular.js is a very nice framework . Developed by Googler's, it has some very interesting design choices.
Pros: Very well thought out with respect to template scoping and controller design. Has a dependency injection system (I am a big fan of IOC). Supports a rich UI-Binding syntax to make things like filtering and transforming values a breeze.
Cons: Codebase appears to be fairly sprawling and not very modular. Views are not modular enough .
Knockout.js is an MVVM framework that receives lots of praise from its supporters. It stresses declarative UI bindings and automatic UI refresh.
Pros: Binding support. Great documentation and amazing tutorial system.
Cons: Awkward binding syntax and lacks a solid view component hierarchy. I want to be able to reuse components easily. I also feel like identifying as an MVVM framework is deleterious. Hardly any of these frameworks are MVC, but are of the MV* variety (MVP, MVVM, etc)
Which framework to use?
A comparison of Angular Vs. Knockout: - http://www.slideshare.net/basarat1/mvvm-knockout-vs-angular
A sample app some guys did in various frameworks:
· TODO App in Knockout [Not bad – but still one file with too many things in it]
· TODO App in Angular [More files, forces you into thinking about structure and avoiding jQuery]
· TODO Apps in other frameworks (for reference only – I don’t think we can spend days evaluating the best framework – and frankly it does not matter that much.)
About that steep learning curve:
I’ve worked with both – it took me almost the same time to get a brand new app running in KO vs Angular. Once I looked at Angular – I remembered all the additional frameworks (require, sammy, amplify, I needed to learn to make a ‘properly designed’ client-side app with KO as the basis.
Other things we considered in choosing AngularJS:
Momentum behind the framework (Google!)
Completeness in terms of client-side application requirements (clean design, testability, data-binding, routing, module loading, ui-widgets)
Plugging into existing apps
Playing well with other frameworks/scripts
In the properties for the project. In the Build Tab. Select "Generate Serialization assembly:" to Off
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
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
- In Choose Commands From, select Commands Not In the Ribbon.
- Locate Document Location, select it, and then click Add to add it to your
Prompt to open a Microsoft Office Word document as read-only
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 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)
2) The <readerQuotas> settings (under the <binding> elements) which has control over the maxarrayLength, maxStringLength ,etc...
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
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
<LogAttribute xmlns="clr-namespace:PostSharp.Toolkit.Diagnostics;assembly:PostSharp.Toolkit.Diagnostics" AttributeTargetAssemblies="Applications.MyApp" AttributeTargetTypes=" Applications.MyApp.MyCustomer" AttributeTargetMembers="*" OnExceptionLevel="Warning" OnExceptionOptions="IncludeParameterValue" />
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).
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)
© Michael Freidgeim
Theme by PiyoDesign. Valid XHTML & CSS.