Serve up Debug Symbols for your NuGet packages? Heck yeah!</h1> <article> <h1>Serve up Debug Symbols for your NuGet packages? Heck yeah!</h1> <p>2015-01-15T15:08:00.001+02:00</p> <div>BOO-YAH!</div><div><br></div><div>When you want to push to the symbol servers you need to use the command shown here. When you want to use the Symbol Server in Visual Studio, you need to use the debugging URL shown here in your Visual Studio's Source Symbol Server setup like so:</div><div><br></div><div><div>Now, test this bad boy out by:</div><div><ol><li>Upload a NuGet package to your own symbol server (as outlined in my previous post)<br></li><li>Push its corresponding Symbols package (created by packaging with symbols via '-symbols' switch) using the push command shown on your new symbol server's page<br></li><li>Create a new project to use the NuGet package published in #1<br></li><li>Add NuGet package to project<br></li><li>Run Project<br></li><li>F11 in to code that utilizes the NuGet project<br></li><li>Watch the magic. You should step in to source, but see that the "file" is coming from a super wacky temp location.<br></li></ol></div><div>That's it, you're all set! Since you're using this for your own NuGet packages, I can't really see a reason *not* to publish symbol packages with your binary ones. Enjoy!</div></div><div><br></div><div><br></div><div>Read more: <a href="http://www.codeproject.com/Articles/864724/Serve-up-Debug-Symbols-for-your-NuGet-packages-Hec">Codeproject</a></div><div><br></div> </article> <article> <h1>Mono for Unreal Engine</h1> <p>2014-11-19T15:31:00.001+02:00</p> <div dir="ltr"><div class="gmail_default" style="text-align:center;font-family:tahoma,sans-serif"><br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif">Earlier this year, both Epic Games and CryTech made their Unreal Engine and CryEngine available under an affordable subscription model. These are both very sophisticated game engines that power some high end and popular games.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">We had previously helped Unity bring Mono as the scripting language used in their engine and we now had a chance to do this over again.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Today I am happy to introduce Mono for Unreal Engine.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">This is a project that allows Unreal Engine users to build their game code in C# or F#.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://tirania.org/blog/archive/2014/Oct-23.html">Personal blog of Miguel de Icaza</a></font></div></div> </div> </article> <article> <h1>Migrating from Silverlight to AngularJS</h1> <p>2014-11-16T14:52:00.001+02:00</p> <div dir="ltr"><div class="gmail_default" style="text-align:center;font-family:tahoma,sans-serif"><br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif">Introduction</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">What attracted many developers to Silverlight starting back in 2007, was that it allowed us to write maintainable web applications quickly and easily. This was largely due to MVVM, a pattern that separates logic from presentation. The ViewModel portion of the app, written in C# or VB, contains all of the logic, which makes it easy to test and maintain. The View portion of the app is written in XAML, using a rich library of supporting classes and controls.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">When Microsoft decided to stop investing in Silverlight, many developers were faced with a tough decision. How could they migrate to modern web platforms and not throw away all the benefits of MVVM and the knowledge they gained by using Silverlight?</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">At ComponentOne, a division of GrapeCity, we faced this challenge ourselves. We studied the alternatives and concluded that HTML5 and application frameworks such as AngularJS seemed like the best option going forward. AngularJS provides the key ingredients: a solid framework for single-page applications, a templating mechanism, and basic support for MVVM. All it was missing were the controls and a few essential classes required to create traditional MVVM apps.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Well, we know how to write controls. So we decided to add what was missing.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">The result is Wijmo 5, our latest control library for HTML5 and JavaScript development. Wijmo 5 is a true HTML5 solution, based on JavaScript and CSS. It includes all of the controls commonly used in LOB (line of business) applications, as well as JavaScript implementations of the ICollectionView interface and a concrete CollectionView class.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Together with AngularJS, Wijmo 5 provides a great platform for porting existing Silverlight applications and also for creating brand new web applications faster than you ever thought possible.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://www.codeproject.com/Articles/841700/Migrating-from-Silverlight-to-AngularJS">Codeproject</a></font></div></div> </div> </article> <article> <h1>Visual Studio 2015 Preview Features – Part 1</h1> <p>2014-11-16T14:18:00.000+02:00</p> <div dir="ltr"><div class="gmail_default" style="text-align:center;font-family:tahoma,sans-serif"> <br><br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif">Visual Studio 2015 Preview has been released with support for cross platform device development in C++ in addition to an Android emulator, updated tooling for Apache Cordova, the open source .NET compiler platform, support for <a href="http://ASP.NET">ASP.NET</a> 5. The preview also includes many new updates and improvements.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Visual Studio 2015 adds support for cross-platform mobile development using C++ leveraging the open source Clang and LLVM toolchain. It enables developers to share, reuse, build, deploy and debug libraries for other operating systems in Visual Studio.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">With the help of Visual Studio 2015 Preview, you will be able to create projects from templates for Android Native Activity apps or for shared code libraries that you can use on multiple platforms and in Xamarin hybrid apps. It is also possible to set breakpoints, watch variables, view the stack and step through code in the Visual Studio debugger.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">In addition to the currently available emulator for Windows Phone, Visual Studio 2015 includes a powerful emulator for Android. This means that you will be able to test Android apps from within Visual Studio.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://java.dzone.com/articles/visual-studio-2015-preview">DZone</a></font></div></div> </div> </article> <article> <h1>Microsoft Open Sources .NET and Mono</h1> <p>2014-11-16T10:19:00.001+02:00</p> <div dir="ltr"><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif">Today, Scott Guthrie announced that Microsoft is open sourcing .NET. This is a momentous occasion, and one that I have advocated for many years.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">.NET is being open sourced under the MIT license. Not only is the code being released under this very permissive license, but Microsoft is providing a patent promise to ensure that .NET will get the adoption it deserves.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">The code is being hosted at the .NET Foundation's github repository.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">This patent promise addresses the historical concerns that the open source, Unix and free software communities have raised over the years.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">.NET Components</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">There are three components being open sourced: the .NET Framework Libraries, .NET Core Framework Libraries and the RyuJit VM. More details below.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">.NET Framework Class Libraries</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">These are the class libraries that power the .NET framework as it ships on windows. The ones that Mono has historically implemented in an open source fashion.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">The code is available today from <a href="http://github.com/Microsoft/referencesource">http://github.com/Microsoft/referencesource</a>. Mono will be able to use as much a it wants from this project.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">We have a project underway that already does this. We are replacing chunks of Mono code that was either incomplete, buggy, or not as fully featured as it should be with Microsoft's code.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://tirania.org/blog/archive/2014/Nov-12.html">Personal blog of Miguel de Icaza</a></font></div></div> </div> </article> <article> <h1>XAML Organization</h1> <p>2014-11-11T13:57:00.000+02:00</p> <div dir="ltr"><div class="gmail_default" style="text-align:center;font-family:tahoma,sans-serif"><br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif">We've worked on countless WPF and Silverlight projects over the past several years and throughout that time, we've refined both our process and the organization of our solutions. We pass off front-end code to our client developers. So clean, understandable organization is extremely important for an effective transfer of knowledge.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Most of the development teams that we work with are well versed with c# code, programming methodologies, and best practices. But typically we find that XAML is not something that they care much about. Due to this lack of interest folks tend to not put much up-front thought into how their Resource Dictionaries are organized, nor is there much in the way of guidance from Microsoft. So then 3 months into their development cycle the application looks great from a code perspective, especially if the Model View ViewModel (MVVM) paradigm is followed, but digging into the various styles, templates, brush resources, etc… reveal a lot of problems.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">...</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">...</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><div class="gmail_default">Rule#1: One Style per Resource Dictionary</div><div class="gmail_default"><br></div><div class="gmail_default">For all but the smallest, apps, you will want to follow this rule. It is much easier to find a style within a directory than if it is buried deep inside of a gigantic "catch-all" Resource Dictionary. It is very similar to the c# rule of one class per file. Now there are exceptions to rule #1, we do occasionally package up more than one style in a Resource Dictionary, but only if there is a tight pairing between styles such as a small supporting style that the main style needs. A good example of this is the button style that a scrollBar uses for "Line up"/"Line Down" buttons. We would package these styles together.</div><div class="gmail_default"><br></div><div class="gmail_default">Rule #2: Resource Dictionary named to match contained style</div><div class="gmail_default"><br></div><div class="gmail_default">Simple enough, if you have a named style called "HelpButtonStyle", name the Resource Directory "HelpButtonStyle.xaml". If you have a nameless style that acts as the default for a control, name the Resource Dictionary the same as the TargetType, for example "ComboBoxStyle.xaml"</div><div class="gmail_default"><br></div><div class="gmail_default">Rule #3: No resources directly in App.xaml (only ResourceDirectory merging)</div></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://projekt202.com/blog/2010/xaml-organization/">Projekt202</a></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div></div> </div> </article> <article> <h1>ILSpy, the Visual Studio Extension</h1> <p>2014-11-10T16:52:00.001+02:00</p> <div dir="ltr"><div class="gmail_default" style="text-align:center;font-family:tahoma,sans-serif"><br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif">Today's Visual Studio Extension is one that can and will come in handy and is a must tool belt have...</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Sometimes you've got an assembly, but no PDB or Source, and you just need to peek at how it works. Years ago, we highlighted the open source decompiler ILSpy, I spy with my little eye... ILSpy.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Today we're highlighting a Visual Studio Extension that makes ILSpy that much easier to use, almost too easy (insert "With great power, comes..." here)</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://channel9.msdn.com/coding4fun/blog/ILSpy-the-Visual-Studio-Extension">Channel9</a></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="https://visualstudiogallery.msdn.microsoft.com/8ef1d688-f80c-4380-8004-2ec7f814e7de">Visual Studio extensions</a></font></div></div> </div> </article> <article> <h1>Differences between nanomsg and ZeroMQ</h1> <p>2014-11-06T14:52:00.001+02:00</p> <div dir="ltr"><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif">Differences between nanomsg and ZeroMQ</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Licensing</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">nanomsg library is MIT-licensed. What it means is that, unlike with ZeroMQ, you can modify the source code and re-release it under a different license, as a proprietary product, etc. More reasoning about the licensing can be found here.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">POSIX Compliance</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">ZeroMQ API, while modeled on BSD socket API, doesn't match the API fully. nanomsg aims for full POSIX compliance.</font></div><div class="gmail_default" style><ul><li><span style="font-family:tahoma,sans-serif">Sockets are represented as ints, not void pointers.</span><br></li><li><span style="font-family:tahoma,sans-serif">Contexts, as known in ZeroMQ, don't exist in nanomsg. This means simpler API (sockets can be created in a single step) as well as the possibility of using the library for communication between different modules in a single process (think of plugins implemented in different languages speaking each to another). More discussion can be found here.</span><br></li><li><span style="font-family:tahoma,sans-serif">Sending and receiving functions (nn_send, nn_sendmsg, nn_recv and nn_recvmsg) fully match POSIX syntax and semantics.</span><br></li></ul></div><div class="gmail_default" style><font face="tahoma, sans-serif">Implementation Language</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">The library is implemented in C instead of C++.</font></div><div class="gmail_default" style><ul><li><span style="font-family:tahoma,sans-serif">From user's point of view it means that there's no dependency on C++ runtime (libstdc++ or similar) which may be handy in constrained and embedded environments.</span><br></li><li><span style="font-family:tahoma,sans-serif">From nanomsg developer's point of view it makes life easier.</span><br></li><li><span style="font-family:tahoma,sans-serif">Number of memory allocations is drastically reduced as intrusive containers are used instead of C++ STL containers.</span><br></li><li><span style="font-family:tahoma,sans-serif">The above also means less memory fragmentation, less cache misses, etc.</span><br></li><li><span style="font-family:tahoma,sans-serif">More discussion on the C vs. C++ topic can be found here and here.</span><br></li></ul></div><div class="gmail_default" style><font face="tahoma, sans-serif">Pluggable Transports and Protocols</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">In ZeroMQ there was no formal API for plugging in new transports (think WebSockets, DCCP, SCTP) and new protocols (counterparts to REQ/REP, PUB/SUB, etc.) As a consequence there were no new transports added since 2008. No new protocols were implemented either. The formal internal transport API (see transport.h and protocol.h) are meant to mitigate the problem and serve as a base for creating and experimenting with new transports and protocols.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Please, be aware that the two APIs are still new and may experience some tweaking in the future to make them usable in wide variety of scenarios.</font></div><div class="gmail_default" style><ul><li><span style="font-family:tahoma,sans-serif">nanomsg implements a new SURVEY protocol. The idea is to send a message ("survey") to multiple peers and wait for responses from all of them. For more details check the article here. Also look here.</span><br></li><li><span style="font-family:tahoma,sans-serif">In financial services it is quite common to use "deliver messages from anyone to everyone else" kind of messaging. To address this use case, there's a new BUS protocol implemented in nanomsg. Check the details here.</span><br></li></ul></div><div class="gmail_default" style><font face="tahoma, sans-serif">Threading Model</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">One of the big architectural blunders I've done in ZeroMQ is its threading model. Each individual object is managed exclusively by a single thread. That works well for async objects handled by worker threads, however, it becomes a trouble for objects managed by user threads. The thread may be used to do unrelated work for arbitrary time span, e.g. an hour, and during that time the object being managed by it is completely stuck. Some unfortunate consequences are: inability to implement request resending in REQ/REP protocol, PUB/SUB subscriptions not being applied while application is doing other work, and similar. In nanomsg the objects are not tightly bound to particular threads and thus these problems don't exist.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><ul><li><span style="font-family:tahoma,sans-serif">REQ socket in ZeroMQ cannot be really used in real-world environments, as they get stuck if message is lost due to service failure or similar. Users have to use XREQ instead and implement the request re-trying themselves. With nanomsg, the re-try functionality is built into REQ socket.</span><br></li><li><span style="font-family:tahoma,sans-serif">In nanomsg, both REQ and REP support cancelling the ongoing processing. Simply send a new request without waiting for a reply (in the case of REQ socket) or grab a new request without replying to the previous one (in the case of REP socket).</span><br></li><li><span style="font-family:tahoma,sans-serif">In ZeroMQ, due to its threading model, bind-first-then-connect-second scenario doesn't work for inproc transport. It is fixed in nanomsg.</span><br></li><li><span style="font-family:tahoma,sans-serif">For similar reasons auto-reconnect doesn't work for inproc transport in ZeroMQ. This problem is fixed in nanomsg as well.</span><br></li><li><span style="font-family:tahoma,sans-serif">Finally, nanomsg attempts to make nanomsg sockets thread-safe. While using a single socket from multiple threads in parallel is still discouraged, the way in which ZeroMQ sockets failed randomly in such circumstances proved to be painful and hard to debug.</span></li></ul><div><font face="tahoma, sans-serif">(+more)</font></div><div><font face="tahoma, sans-serif"><br></font></div></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://nanomsg.org/documentation-zeromq.html">nanomsg.org</a></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div></div> </div> </article> <article> <h1>dot42 - C# for Android</h1> <p>2014-11-03T13:27:00.000+02:00</p> <div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif"><br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><div class="gmail_default">In a nutshell</div><div class="gmail_default"><br></div><div class="gmail_default">Write Android apps in C# without any runtime requirements such as Mono, resulting in small packages. </div><div class="gmail_default">Run, deploy and debug right from Visual Studio or SharpDevelop. </div><div class="gmail_default">By design, all Android devices are supported.</div><div class="gmail_default"><br></div><div class="gmail_default">Read more: <a href="https://www.dot42.com/">dot42</a></div></div> </div> </article> <article> <h1>#1,185 – ItemsControl Customization Summary</h1> <p>2014-10-22T15:39:00.001+03:00</p> <div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif"><div class="gmail_default">You can can customize an ItemsControl, or any of the controls that derive from it (ComboBox, DataGrid, ListBox, TabControl, TreeView et al), in a number of ways. The various customization mechanisms are summarized below.</div><div class="gmail_default"><ul><li>Set Style to apply a set of property values for the main control<br></li><li>Set Template to change the control template of the control.<br></li><ul><li>This changing the highest level of the control (e.g. for a ListBox, a Border wrapping a ScrollViewer, in turn wrapping an ItemsPresenter)</li></ul><li>Set ItemsPanel to change the panel used to lay out the individual items<br></li><ul><li>E.g. User horizontally oriented StackPanel to lay out ListBox items horizontally, rather than vertically</li></ul><li>Set ItemContainerStyle to set properties that apply to the container for each item<br></li><ul><li>E.g. Properties that apply to each ListBoxItem within a ListBox</li></ul><li>Set ItemTemplate to change the data template used to render each item in the list<br></li><ul><li>E.g. Create a custom layout for each item in a ListBox</li></ul></ul></div><div class="gmail_default"><br></div><div class="gmail_default">Read more: <a href="http://wpf.2000things.com/2014/10/22/1185-itemscontrol-customization-summary/">2,000 Things You Should Know About WPF</a></div></div> </div> </article> <article> <h1>Visual Studio 2013 Update 4 RC now Available</h1> <p>2014-10-22T11:31:00.000+03:00</p> <div dir="ltr"><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif">Visual Studio 2013 Update 4 RC is now available to download. This release has lots of small features and fixes for <a href="http://ASP.NET">ASP.NET</a> and web platform, Team Foundation Server, Visual C++, JavaScript Editor, Testing Tools, and some other areas. Specifically for updates to the web development tools checkout this new features announcement on .NET web development and tools blog.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">The release notes have the complete list of features and fixes included in this release.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://www.microsoft.com/en-us/download/details.aspx?id=44545">MS Download</a></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://blogs.msdn.com/b/visualstudio/archive/2014/10/16/visual-studio-2013-update-4-rc-now-available.aspx">The Visual Studio Blog</a></font></div></div> </div> </article> <article> <h1>Батники против эксплойтов</h1> <p>2014-10-21T18:32:00.001+03:00</p> <div dir="ltr"><div class="gmail_default" style><font face="tahoma, sans-serif">Я понимаю, что для всех батники выглядят как нечто очень простое и со времен AUTOEXEC.BAT уже практически забытое, в то же время эксплойты, если вы конечно не профессиональный исследователь уязвимостей, выглядят очень сложно и практически неправдоподобно, особенно для некоторых разработчиков. Но! В данном посте я постараюсь перевернуть эти представления и рассказать, что всё как будто наоборот. Батники чуть легче и сильнее по функционалу brainfuck'а, а эксплойты не страшнее сортировки пузырьком на basic'е. </font><br></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><div class="gmail_default">Как я до этого дошел?</div><div class="gmail_default"><br></div><div class="gmail_default">Мне тут на глаза попалась коробка с Windows 7 x64 c минимальными системными требованиями в 2 ГБ оперативной памяти! И я тут подумал, неужели во всех этих гигабайтах не найдётся пары килобайт кода, которые могли бы защитить пользователей от такой напасти, как эксплойты и Drive-by? Это бич всех ОС от MS уже лет пять! Должны быть там средства для хоть какой-то защиты? Но как их заюзать, да еще и стандартными средствами? С помощью батников. А как? Чтобы это понять, нужно прочитать эту простыню до конца. 8) </div><div class="gmail_default"><br></div><div class="gmail_default">Теория</div><div class="gmail_default"><br></div><div class="gmail_default">В упрощенной теории срабатывания эксплойтов всё выглядит так: «что-то где-то посмотрели, что-то где-то послали, что-то где-то запустилось». В реальной жизни это часто выглядит так: пользователь, гуляя по интернетам, попадает на честно взломанный сайт, где ему вместе с полезной информацией отдают или JavaScript или редирект на JavaScript, который, анализируя USER-AGENT, информацию о плагинах и т.д. выдаёт пользователю эксплойт, который точно у пользователя сработает. После этого на машину пользователя сгружается троянец, запускается, прописывается в системе и начинает делать свои грязные дела. </div><div class="gmail_default"><br></div><div class="gmail_default">Read more: <a href="http://habrahabr.ru/company/kaspersky/blog/137304/">Habrahabr.ru</a></div></font></div> </div> </article> <article> <h1>Visual Studio "14" CTP</h1> <p>2014-06-05T09:13:00.001+03:00</p> <div dir="ltr"><div class="gmail_default"><div class="gmail_default" style="text-align:center"><font face="tahoma, sans-serif"><div><br> </div><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"> Today, we are making available a first community technology preview of the next version of Visual Studio, codenamed Visual Studio "14". This early build is focused on enabling feedback and testing from the Visual Studio community. Visual Studio "14" will most likely be available sometime in 2015, with a more complete preview release and final naming available later this year. Given that this is a very early build, please install in a test environment with no earlier versions of Visual Studio installed.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">You can read about the new features and known issues in this first Visual Studio "14" CTP, and also download today.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Over the last 3 months, we've announced many exciting technologies that will be important parts of Visual Studio "14" - including the "Roslyn" .NET compiler platform, <a href="http://ASP.NET">ASP.NET</a> vNext and Apache Cordova tooling. The Visual Studio "14" CTP 1 includes a few of these tools, as well as many additional improvements across Visual Studio, including an early look at some new C++ 11 support that will be part of Visual Studio "14".</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">C# and VB with the .NET Compiler Platform ("Roslyn")</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">In Visual Studio "14", the C# and VB compilers and IDE support are fully built on the .NET Compiler Platform ("Roslyn"). This open-source compiler as a service now sits behind dozens of developer experiences in Visual Studio "14", powering build, IntelliSense, refactoring, CodeLens, debugging and many more features developers use every day. In most places the experiences are unchanged, but there have also been many small improvements across the entire development experience as part of the new compiler platform.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: </font><a href="http://blogs.msdn.com/b/somasegar/archive/2014/06/03/first-preview-of-visual-studio-quot-14-quot-available-now.aspx">Somasegar's blog</a></div> <div class="gmail_default" style>Read more: <a href="http://www.visualstudio.com/en-us/downloads/visual-studio-14-ctp-vs">Visual Studio</a></div></div> </div> </article> <article> <h1>#466 – Using a GridSplitter in Conjunction with a SharedSizeGroup</h1> <p>2014-05-19T09:46:00.001+03:00</p> <div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif"><div style="text-align:center"></div><br></div> <div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif">A GridSplitter allows a user to change the size of a row or column by dragging a visual splitter. A SharedSizeGroup allows two rows or columns to automatically have the same size. You can combine these concepts, allowing a user to change the size of one column and have another column automatically have the same size.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif">In the example below, the user can drag either splitter, but when dragging, the width of both left and right columns changes at the same time.</font></div> <div class="gmail_default" style> <font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><div class="gmail_default"><Grid Grid.IsSharedSizeScope="True"></div><div class="gmail_default"> <Grid.ColumnDefinitions></div><div class="gmail_default"> <ColumnDefinition SharedSizeGroup="A" Width="Auto"/></div><div class="gmail_default"> <ColumnDefinition Width="Auto"/></div> <div class="gmail_default"> <ColumnDefinition/></div><div class="gmail_default"> <ColumnDefinition Width="Auto"/></div><div class="gmail_default"> <ColumnDefinition SharedSizeGroup="A" Width="Auto"/></div> <div class="gmail_default"> </Grid.ColumnDefinitions></div><div class="gmail_default"> </div><div class="gmail_default"> <Label Content="Left" Background="Azure" Grid.Column="0"/></div> <div class="gmail_default"> <Label Content="Middle" Background="Lavender" Grid.Column="2"/></div><div class="gmail_default"> <Label Content="Right" Background="Moccasin" Grid.Column="4"/></div> <div class="gmail_default"> </div><div class="gmail_default"> <GridSplitter Grid.Column="1" Width="8" Background="DarkSlateBlue"</div><div class="gmail_default"> HorizontalAlignment="Center" VerticalAlignment="Stretch"/></div> <div class="gmail_default"> <GridSplitter Grid.Column="3" Width="8" Background="DarkSlateBlue"</div><div class="gmail_default"> HorizontalAlignment="Center" VerticalAlignment="Stretch"/></div> <div class="gmail_default"></Grid></div></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><span style="font-family:tahoma,sans-serif">Read more: </span><font face="tahoma, sans-serif"><a href="http://wpf.2000things.com/tag/sharedsizegroup/">2,000 Things You Should Know About WPF</a></font><br> </div></div> </div> </article> <article> <h1>#575 – PropertyMetadata vs. FrameworkPropertyMetadata</h1> <p>2014-05-13T10:36:00.001+03:00</p> <div dir="ltr"><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif"> When you implement a custom dependency property and you register the property by calling DependencyProperty.Register, you specify some metadata for the property by passing it an instance of PropertyMetadata. This can be an instance of the PropertyMetadata class or an instance of one of its subclasses. The differences are shown below.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">PropertyMetadata – Basic metadata relating to dependency properties</font></div> <div class="gmail_default" style><ul><li><span style="font-family:tahoma,sans-serif">CoerceValueCallback – coerce the value when being set</span><br></li><li><span style="font-family:tahoma,sans-serif">DefaultValue – a default value for the property</span><br> </li><li><span style="font-family:tahoma,sans-serif">PropertyChangedCallback – respond to new effective value for the property</span><br></li></ul></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br> </font></div><div class="gmail_default" style><font face="tahoma, sans-serif">UIPropertyMetadata – derives from PropertyMetadata and adds:</font></div><div class="gmail_default" style><ul><li><span style="font-family:tahoma,sans-serif">IsAnimationProhibited – disable animations for this property?</span><br> </li></ul></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">FrameworkPropertyMetadata – derives from UIPropertyMetadata and adds:</font></div> <div class="gmail_default" style><ul><li><span style="font-family:tahoma,sans-serif">AffectsArrange, AffectsMeasure, AffectsParentArrange, AffectsParentMeasure, AffectsRender – Should layout calculations be re-run after property value changes?</span><br> </li><li><span style="font-family:tahoma,sans-serif">BindsTwoWayByDefault, DefaultUpdateSourceTrigger, IsDataBindingAllowed, IsNotDataBindable – Dictates how property participates in data binding</span><br></li><li><span style="font-family:tahoma,sans-serif">Inherits, OverridesInheritanceBehavior – Does inheritance work for this property?</span><br> </li><li><span style="font-family:tahoma,sans-serif">Journal – Store this value when journaling?</span><br></li><li><span style="font-family:tahoma,sans-serif">SubPropertiesDoNotAffectRender – Check properties of this object when layout changes?</span><br> </li></ul></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://wpf.2000things.com/tag/frameworkpropertymetadata/">2,000 Things You Should Know About WPF</a></font></div> </div> </div> </article> <article> <h1>How to build Mono 3.4.0 / 3.4.1 on Windows</h1> <p>2014-05-12T10:11:00.000+03:00</p> <div dir="ltr"><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif">Introduction</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style> <font face="tahoma, sans-serif">This article builds on and updates a number of existing articles which attempt to describe the build process for Mono on Windows.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br> </font></div><div class="gmail_default" style><font face="tahoma, sans-serif">If you are just looking for Mono 3.4.0 binaries to use, I have provided the resulting binaries from this walk-through here.</font></div><div class="gmail_default" style> <font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">The baseline instructions from the Mono project can be found here.</font></div><div class="gmail_default" style> <font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">In theory these should be enough to get Mono compiled but, as ever in the real world, things are slightly more complex. As a result others have written pieces on how to build Mono, and I have found "Building Mono on Windows: The Final Battle" particularly useful.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">That said, these articles are now a few years old and I ran into various issues building Mono which I have attempted to address with the walk-through below,</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">We are going to look both at building from the current, at the time of writing, Mono release tarball (3.4.0) and then at building the "latest and greatest" directory out of the git repository</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">The sequence of events is as follows,</font></div><div class="gmail_default" style> <font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Install pre-compiled Mono</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Install & configure Cygwin</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif">Retrieve and extract tarball Mono Sources</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Build and Mono</font></div><div class="gmail_default" style> <font face="tahoma, sans-serif">Modify Cygwin/Mono to address any build failures</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Install Mono and modify installation</font></div><div class="gmail_default" style> <font face="tahoma, sans-serif">Fix-ups/workarounds for Xamarin Studio</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Retrieve and build git Mono Sources</font></div><div class="gmail_default" style> <font face="tahoma, sans-serif">This walk-through has been tested on an x64 machine running Windows 8.1.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Install pre-compiled Mono binaries</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">A stable, pre-compiled build of Mono 3.2.3 can be downloaded here. Download and install this.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Check that it runs by opening a Mono command prompt from the start bar and typing</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><span style="font-family:tahoma,sans-serif">mono --version </span><br></div><div class="gmail_default" style> <font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">You should see Mono come up and the 3.2.3 version shown</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br> </font></div><div class="gmail_default" style><span style="font-family:tahoma,sans-serif">C:\Program Files (x86)\Mono-3.2.3>mono --version</span><br></div><div class="gmail_default" style><font face="tahoma, sans-serif">Mono JIT compiler version 2.10.9 (tarball)</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif">Copyright (C) 2002-2011 Novell, Inc, Xamarin, Inc and Contributors. www.mono-pro</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><a href="http://ject.com">ject.com</a></font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"> TLS: normal</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"> SIGSEGV: normal</font></div><div class="gmail_default" style> <font face="tahoma, sans-serif"> Notification: Thread + polling</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"> Architecture: x86</font></div><div class="gmail_default" style> <font face="tahoma, sans-serif"> Disabled: none</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"> Misc: softdebug</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"> LLVM: supported, not enabled.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"> GC: Included Boehm (with typed GC and Parallel Mark)</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">C:\Program Files (x86)\Mono-3.2.3> </font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://www.codeproject.com/Articles/769292/How-to-build-Mono-on-Windows">Codeproject</a></font></div> </div> </div> </article> <article> <h1>Visual Studio 2013 Update 2 RC</h1> <p>2014-05-07T18:28:00.001+03:00</p> <div dir="ltr"><div class="gmail_default" style><font face="tahoma, sans-serif">This is a release candidate (RC) for Visual Studio 2013 Update 2.</font><br></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br> </font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://www.microsoft.com/en-us/download/details.aspx?id=42307">MS Downloads</a></font></div> </div> </article> <article> <h1>Lowering in language design, part one</h1> <p>2014-05-01T18:06:00.001+03:00</p> <div dir="ltr"><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif">Programming language designers and users talk a lot about the "height" of language features; some languages are considered to be very "high level" and some are considered to be very "low level". A "high level" language is generally speaking one which emphasizes the business concerns of the program, and a low-level language is one that emphasizes the mechanisms of the underlying hardware. As two extreme examples, here's a program fragment in my favourite high-level language, Inform7:</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Overlying relates one thing to various things. The verb to</font></div><div class="gmail_default" style> <font face="tahoma, sans-serif">overlie (it overlies, they overlie, it is overlying) implies </font></div><div class="gmail_default" style><font face="tahoma, sans-serif">the overlying relation. </font></div><div class="gmail_default" style> <font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">The jacket overlies the shirt. The shoes overlie the socks. </font></div><div class="gmail_default" style> <font face="tahoma, sans-serif">The slacks overlie the undershorts. The shirt overlies the</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif">undershirt.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Before wearing something when something (called the impediment)</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif">which overlies the noun is worn by the player: try taking off</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">the impediment; if the player is wearing the impediment, stop </font></div> <div class="gmail_default" style><font face="tahoma, sans-serif">the action.</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">This is part of the source code of a game;1 specifically, this is the code that adds a rule to the game that describes what happens when a player attempts to put on a pair of socks while wearing shoes. Note that the function which takes two objects and returns a Boolean indicating whether one overlies the other is not written as a function but rather as a relation associated with a verb, and that the language even allows you to provide a conjugation for a non-standard verb so that you can use it in any natural English form in your program. It is hard to imagine a language getting closer to the business domain.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">By contrast, x86 assembler is a very low-level language:</font></div><div class="gmail_default" style> <font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">add ebx, eax</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">neg ebx </font></div> <div class="gmail_default" style><font face="tahoma, sans-serif">add eax, ebx</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">dec ecx</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br> </font></div><div class="gmail_default" style><font face="tahoma, sans-serif">In one sense we know exactly what this fragment is doing; adding, negating and decrementing the values in registers eax, ebx and ecx. Why? Hard to say. The business domain is nowhere found here; this is all mechanism.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://ericlippert.com/2014/04/28/lowering-in-language-design-part-one/">Fabulous adventures in coding</a></font></div> </div> </div> </article> <article> <h1>WPF: Inheriting from custom class instead of Window</h1> <p>2014-04-23T17:49:00.001+03:00</p> <div dir="ltr"><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif">In <a href="http://ASP.NET">ASP.NET</a>, we learned that it is often interesting to inherit from another class than from System.Web.UI.Page. This allows to define common methods, such as utilities, etc... which are used by a set of web pages throughout an application.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif">In WPF, it's also possible to do the same, and to inherit from a custom class instead of System.Windows.Window, of System.Windows.Controls.Page, or of System.Windows.Controls.UserControl for example.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif">When you add a Window (or Page, or UserControl...) to a WPF project, the chain of inheritance is as follows:</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br> </font></div><div class="gmail_default" style="text-align:center"><font face="tahoma, sans-serif"><br><br></font></div><div class="gmail_default" style> <font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">If you have a special method "doSomething()" which you want to reuse in every Window in the application, then you can store it in an abstract class GalaSoftLb.Wpf.WindowBase and modify the inheritance as follows:<br> </font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style="text-align:center"><font face="tahoma, sans-serif"><br> <br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><div class="gmail_default">In the diagrams above, the Window class is the framework's one, and the class GalaSoftLb.Wpf.WindowBase is abstract.</div> <div class="gmail_default">In order to get the new Windows to derive from this abstract class, not only the C# code must be modified, but also the XAML code. This is a little tricky, because a special syntax must be used. Instead of the usual:</div> <div class="gmail_default"><br></div><div class="gmail_default"><Window x:Class="WindowsApplication1.Window1"</div><div class="gmail_default"> xmlns="<a href="http://schemas.microsoft.com/winfx/2006/xaml/presentation">http://schemas.microsoft.com/winfx/2006/xaml/presentation</a>"</div> <div class="gmail_default"> xmlns:x="<a href="http://schemas.microsoft.com/winfx/2006/xaml">http://schemas.microsoft.com/winfx/2006/xaml</a>"</div><div class="gmail_default"> Title="WindowsApplication1" Height="300" Width="300"</div> <div class="gmail_default"> ></div><div class="gmail_default"> <Grid> </div><div class="gmail_default"> </Grid></div><div class="gmail_default"></Window></div><div class="gmail_default"><br> </div><div class="gmail_default">We have instead:</div><div class="gmail_default"><br></div><div class="gmail_default"><<b>src:WindowBase</b> x:Class="WindowsApplication1.Window1"</div><div class="gmail_default"> xmlns="<a href="http://schemas.microsoft.com/winfx/2006/xaml/presentation">http://schemas.microsoft.com/winfx/2006/xaml/presentation</a>"</div><div class="gmail_default"> xmlns:x="<a href="http://schemas.microsoft.com/winfx/2006/xaml">http://schemas.microsoft.com/winfx/2006/xaml</a>"</div> <div class="gmail_default"> <b> xmlns:src="clr-namespace:GalaSoftLb.Wpf" </b></div><div class="gmail_default"> Title="WindowsApplication1" Height="300" Width="300"</div><div class="gmail_default"> ></div><div class="gmail_default"> <Grid></div><div class="gmail_default"> </Grid></div><div class="gmail_default"></src:WindowBase></div></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br> </font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://geekswithblogs.net/lbugnion/archive/2007/03/02/107747.aspx">Laurent Bugnion (GalaSoft)</a></font></div><div class="gmail_default" style> <font face="tahoma, sans-serif"><br></font></div></div> </div> </article> <article> <h1>Dart on Raspberry Pi.</h1> <p>2014-04-16T18:03:00.000+03:00</p> <div dir="ltr"><div class="gmail_default" style><font face="tahoma, sans-serif">Building Dart VM for the Raspberry Pi.</font><br></div><div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style> <font face="tahoma, sans-serif"><div class="gmail_default">Introduction</div><div class="gmail_default">These instructions will let you build and run the Dart standalone VM for a Raspberry Pi device running the Raspbian distribution of Linux. For now, this process will likely only work on a Linux machine.</div> <div class="gmail_default"><br></div><div class="gmail_default">Build</div><div class="gmail_default">First, grab the Dart source as described in PreparingYourMachine and GettingTheSource.</div><div class="gmail_default"> <br></div><div class="gmail_default">Cross-compile</div><div class="gmail_default">This build will require a cross-compiler that you can obtain by cloning this repository from github.</div><div class="gmail_default"><br> </div> <div class="gmail_default">You can specify the cross-compiler to the build.py command using the --toolchain argument, as follows. From your Dart checkout:</div><div class="gmail_default"><br></div><div class="gmail_default"> $ ./tools/build.py -m release -a arm \</div><div class="gmail_default"> --toolchain=/path/to/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/arm-linux-gnueabihf \</div><div class="gmail_default"> runtime</div> <div class="gmail_default">You'll find the build products under out/ReleaseXARM/. You can optionally strip the dart binary to make it smaller:</div><div class="gmail_default"><br></div><div class="gmail_default">$ /path/to/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/arm-linux-gnueabihf-strip \</div> <div class="gmail_default"> out/ReleaseXARM/dart</div><div class="gmail_default">Run on Hardware</div><div class="gmail_default">To run Dart programs on the Pi, we'll need to create a dart-sdk using the host toolchain:</div> <div class="gmail_default"><br></div><div class="gmail_default">$ ./tools/build.py -m release -a ia32 runtime create_sdk</div><div class="gmail_default">Then, we'll upload this sdk to the device:</div><div class="gmail_default"> <br></div><div class="gmail_default">$ scp -r out/ReleaseIA32/dart-sdk pi@[raspberry pi ip address]:./dart-sdk</div><div class="gmail_default"><br></div><div class="gmail_default">Read more: <a href="https://code.google.com/p/dart/wiki/RaspberryPi">Dart [Google code]</a></div> </font></div> </div> </article> <article> <h1>#153 – Returning a Subset of Array Elements Matching a Particular Criteria</h1> <p>2014-04-14T10:00:00.001+03:00</p> <div dir="ltr"><div class="gmail_default" style><div class="gmail_default" style><font face="tahoma, sans-serif"> Because System.Array implements the IEnumerable interface and because LINQ extends IEnumerable, you can use the IEnumerable.Where method on arrays to find a subset of elements that match a particular criteria.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif"> The Where method accepts a delegate to a function that takes a single element of the same type as the array and returns a boolean value, indicating whether a match is found. Where returns an IEnumerable collection, which can be iterated on to get the elements in the subset.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Here's an example, finding the set of passing scores in a set of scores.</font></div> <div class="gmail_default" style><span style="font-family:tahoma,sans-serif"><br></span></div><div class="gmail_default" style><span style="font-family:tahoma,sans-serif">int[] scores = { 89, 98, 72, 100, 68 };</span><br> </div><div class="gmail_default" style><span style="font-family:tahoma,sans-serif">// Count number of passing grades</span><br></div><div class="gmail_default" style><font face="tahoma, sans-serif">int numPassed = scores.Where((Func<int,bool>)IsPassingGrade).Count();</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Here's the implementation of IsPassingGrade.</font></div><div class="gmail_default" style> <span style="font-family:tahoma,sans-serif"><br></span></div><div class="gmail_default" style><span style="font-family:tahoma,sans-serif">static bool IsPassingGrade(int score)</span><br></div><div class="gmail_default" style> <font face="tahoma, sans-serif">{</font></div><div class="gmail_default" style><font face="tahoma, sans-serif"> return (score >= 75);</font></div><div class="gmail_default" style><font face="tahoma, sans-serif">}</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">You can avoid defining a separate function by using a lamba expression.</font></div> <div class="gmail_default" style><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style><font face="tahoma, sans-serif">Read more: <a href="http://csharp.2000things.com/tag/ienumerable-where/">2,000 Things You Should Know About C#</a></font></div> </div> </div> </article> <article> <h1>Intel(R) Atom™ x86 Image for Android* KitKat 4.4 Installation Instructions - Recommended</h1> <p>2014-04-01T18:19:00.001+03:00</p> <div dir="ltr"><div class="gmail_default"><div class="gmail_default"><font face="tahoma, sans-serif">Introduction</font></div><div class="gmail_default"><font face="tahoma, sans-serif">This document will guide you through installing the Intel® Atom™ x86 image for Android* KitKat, which can be used for development on Intel's x86 architecture.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Prerequisites</font></div><div class="gmail_default"><font face="tahoma, sans-serif">The Android x86 Emulator Image requires the Android SDK to be installed. For instructions on installing and configuring the Android SDK, refer to the Android developer website (<a href="http://developer.android.com/sdk/">http://developer.android.com/sdk/</a>).</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Optional: The x86 Emulator Image for Android can be accelerated using Intel Hardware Accelerated Execution Manager (HAXM). For more information, refer to the "Optimization" section of this document.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Installation</font></div><div class="gmail_default"><font face="tahoma, sans-serif">Downloading through Android SDK Manager</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Start the Android SDK Manager.</font></div><div class="gmail_default"><font face="tahoma, sans-serif">Under "Android 4.4 (API 19)", select "Intel x86 Atom System Image":</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default" style="text-align:center"><font face="tahoma, sans-serif"><br> </font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Read more: <a href="http://www.codeproject.com/Articles/734115/Intel-Atom-x-Image-for-Android-KitKat-Instal">Codeproject</a></font></div> </div> </div> </article> <article> <h1>Creating your first HTML5 spaceship game for the Android* OS on Intel(R) Architecture</h1> <p>2014-04-01T18:18:00.001+03:00</p> <div dir="ltr"><div class="gmail_default"><div class="gmail_default"><font face="tahoma, sans-serif">Introduction</font></div><div class="gmail_default"><font face="tahoma, sans-serif">I'm certain most of us have some insane or not so insane video game plans in mind. The majority of these thoughts are never acted on as many people think game coding is exceptionally hard to do. Indeed that is true to a degree, but it is not as hard as you may think.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">If you have a fundamental understanding of HTML, CSS, and JavaScript*, you have all the requisites to start a straightforward project.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Adding a Canvas element to a web page</font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br> </font></div><div class="gmail_default"><font face="tahoma, sans-serif">One of the most exciting features of HTML5 is the <canvas> element that can be used to draw vector graphics and engender astonishing effects, interactive games, and animations The web defines canvas, as a rectangular area that allows for dynamic, scriptable rendering of 2D shapes and bitmap images. The HTML5 Canvas is perfect for creating great visual results that augment UIs, diagrams, photo albums, charts, graphs, animations, and embedded drawing applications. HTML5 Canvas works with JavaScript libraries and CSS3 enabling you to create interactive web-based games and animations.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">The elementary code for using and setting a canvas looks like this:</font></div><div class="gmail_default"> <font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><span style="font-family:tahoma,sans-serif"><body onload="spaceShipGame()"></span><br></div><div class="gmail_default"><font face="tahoma, sans-serif"> <h1></font></div> <div class="gmail_default"><font face="tahoma, sans-serif"> SpaceShipGame</font></div><div class="gmail_default"><font face="tahoma, sans-serif"> </h1></font></div><div class="gmail_default"><font face="tahoma, sans-serif"> <canvas id="spaceCanvas" width="300" height="300"></font></div> <div class="gmail_default"><font face="tahoma, sans-serif"> </canvas></font></div><div class="gmail_default"><font face="tahoma, sans-serif"> </body></font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br> </font></div><div class="gmail_default"><font face="tahoma, sans-serif">This looks very similar to the <img> element, the difference being that it doesn't have the src and alt attributes. The <canvas> element has only two characteristics, width and height. If your renderings seem inaccurate, try designating your width and height attributes explicitly in the <canvas> attributes, instead of CSS. The width and height attributes default to 300 and 300, respectively. The id will be acclimated to initialize the canvas using JavaScript, and the text next to the equal to sign will be used as a call back when the mobile browser doesn't support it.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Drawing the background and spaceship for a game using HTML5 canvas and JavaScript</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><span style="font-family:tahoma,sans-serif">canvas = document.getElementById("spaceCanvas");</span><br></div> <div class="gmail_default"><font face="tahoma, sans-serif">ctx = canvas.getContext("2d");</font></div><div class="gmail_default"><font face="tahoma, sans-serif">The variable canvas creates the canvas that we need to draw graphics objects, and ctx holds the rendering context. In this case it is a 2d graphics object.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">This context contains the elementary methods for drawing on the canvas such as arc(), lineto(), and fill().</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Next we paint the background black, place shiny asteroids on it, and draw the spaceship using the context object.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><span style="font-family:tahoma,sans-serif">// Paint it black</span><br></div><div class="gmail_default"><font face="tahoma, sans-serif"> ctx.fillStyle = "black";</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"> ctx.rect(0, 0, 300, 300);</font></div><div class="gmail_default"><font face="tahoma, sans-serif"> ctx.fill();</font></div><div class="gmail_default"> <font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif"> // Draw 100 stars.</font></div><div class="gmail_default"><font face="tahoma, sans-serif"> for (i = 0; i <= 100; i++) {</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"> // Get random positions for stars.</font></div><div class="gmail_default"><font face="tahoma, sans-serif"> var x = Math.floor(Math.random() * 299)</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"> var y = Math.floor(Math.random() * 299)</font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"> <font face="tahoma, sans-serif"> // Make the stars white</font></div><div class="gmail_default"><font face="tahoma, sans-serif"> ctx.fillStyle = "white";</font></div><div class="gmail_default"> <font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif"> // Give the spaceship some room.</font></div><div class="gmail_default"><font face="tahoma, sans-serif"> if (x < 20 || y < 20) ctx.fillStyle = "black";</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif"> // Draw an individual star.</font></div><div class="gmail_default"><font face="tahoma, sans-serif"> ctx.beginPath();</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"> ctx.arc(x, y, 3, 0, Math.PI * 2, true);</font></div><div class="gmail_default"><font face="tahoma, sans-serif"> ctx.closePath();</font></div><div class="gmail_default"> <font face="tahoma, sans-serif"> ctx.fill();</font></div><div class="gmail_default"><font face="tahoma, sans-serif"> }</font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div> <div class="gmail_default"><font face="tahoma, sans-serif">Read more: <a href="http://www.codeproject.com/Articles/734112/Creating-your-first-HTML-spaceship-game-for-the-A">Codeproject</a></font></div></div> </div> </article> <article> <h1>Дружим Git с Putty</h1> <p>2014-04-01T18:17:00.000+03:00</p> <div dir="ltr"><div class="gmail_default"><div class="gmail_default"><font face="tahoma, sans-serif"> <br> </font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Итак, представим, что у нас девственно чистая система, в которой нет ни Putty, ни msysgit. Приступим к настройке нашего рабочего окружения.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Установка Putty</font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br> </font></div><div class="gmail_default"><font face="tahoma, sans-serif">Качаем, устанавливаем, генерим и настраиваем ключ c Pagent (инструкция, ?).</font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br> </font></div><div class="gmail_default"><font face="tahoma, sans-serif">Добавляем ключ на git-сервер</font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Копируем публичный OpenSSH ключ из Putty-ключа</font></div> <div class="gmail_default"><font face="tahoma, sans-serif">Открываем страницу с SSH ключами и добавляем из буфера наш ключ</font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"> <font face="tahoma, sans-serif">В картинках (на примере GitHub)</font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Создаём и сохраняем в Putty профиль «<a href="mailto:git@github.com">git@github.com</a>» и проверяем, что удаётся зайти по ключу – должна открыться и сразу закрыться консоль.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Read more: <a href="http://habrahabr.ru/post/217869/">Habrahabr.ru</a></font></div></div> </div> </article> <article> <h1>Rhino Mocks 4.0.0 Alpha Released</h1> <p>2014-04-01T13:08:00.001+03:00</p> <div dir="ltr"><div class="gmail_default"><div class="gmail_default"><font face="tahoma, sans-serif">It has been a little longer than expected but the latest version of Rhino Mocks has been released and is available from NuGet. You can download the package from here:</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif"><a href="https://www.nuget.org/packages/RhinoMocks/4.0.0-alpha">https://www.nuget.org/packages/RhinoMocks/4.0.0-alpha</a></font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">This is an "alpha" release since there are more than likely going to be a few things that come up. As a matter of fact, there are two things that I am already thinking about changing.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">One is to be a little more explicit with arranging expectations against properties. Right now when you arrange an expectation against a property the intent is inferred. Instead I think it would be better to be explicit by adding ExpectPropertyGet and ExpectPropertySet.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">The other is more of an internal modification to help track expectations easier. Currently an expectation is stored in a single data structure which includes the method, arguments, constraints and return values. When a method is intercepted all of the expectations have to be checked to find a match (clearly there are short circuits but… you get the idea). This modification will help account for how many times a method has (or hasn't) be called and increase performance.</font></div> <div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">Read more: <a href="http://meisinger2.wordpress.com/2014/03/31/rhino-mocks-4-0-0-alpha-released/">Refactoring… Me</a></font></div> </div> </div> </article> </main></body></html>