|
|
browse.develop.com
Browse.develop.com is a community that was established to collect and
organize valuable web information. Our technical staff have selected and
indexed information and courses that they feel will help you stay
current on best practices across the SDLC.
|
17 Articles match "Namespace","Objects"
|
Related DevelopMentor Courses
|
MORE
|
|
Essential LINQ with the Entity Framework
The latest version of the C# programming language comes with many new features intended to increase developer productivity, including automatic properties, object initializers, collection initializers, and partial methods. LINQ to Objects The central feature of.NET 3.5 Now we can group, sort, and filter in-memory collections of objects. LINQ to XML offers an approach to XML queries that is element-centric and makes managing namespaces more straightforward. In this course, you learn to: Leverage new features of C# 3.0, When should I choose one over the other?
DevelopMentor Courses
- Friday, June 12, 2009
Foundations of C# Programming and the.NET Framework
Examine core language features such as types, variables, and control constructs Use object-oriented features such as class, interface, protection, and inheritance Perform error notification and error handling using exceptions Use properties to implement the private data/public accessor pattern Use namespaces to group related types Use delegates and events to implement callbacks Override Object class methods such as ToString Avoid dll conflicts during deployment Use dynamic binding and polymorphism to write generic code (i.e., less code!) interface vs. field)?
DevelopMentor Courses
- Friday, June 12, 2009
Virtual Foundations of C# Programming and the.NET Framework (Part 1)
Examine core language features such as types, variables, and control constructs Use object-oriented features such as class, interface, protection, and inheritance Use properties to implement the private data/public accessor pattern Avoid dll conflicts during deployment Virtual Foundations of C# Programming and the.NET Framework is ".NET Explore core C# features like classes, inheritance, namespaces, and events. Day 2 Class A class is a key object-oriented programming concept and the primary unit of coding in C#. NET 101" for developers moving to.NET. interface vs. field)?
DevelopMentor Courses
- Wednesday, February 17, 2010
|
40 Articles match "Namespace","Objects"
|
The Latest from DevelopMentor
|
MORE
|
|
Silverlight 4 and ICommand
This ICommand property can then be used for databinding a button control (I removed the default namespace declarations): < HyperlinkButton Content ="About" Name ="hyperlinkButton1" HorizontalAlignment ="Center" Command ="{Binding About}" /> See how the ‘Command’-property of the button binds against ‘About’-property of the MainView class? Silverlight 4 offers the opportunity to databind against a command. This is useful in MVVM scenarios. null ) { _executeMethod( parameter ); } } #endregion } #endregion QuickCommand. Sweet!
The Blomsma Code
- Monday, May 24, 2010
MVVM: IUIVisualizer and event management with behaviors
namespace PictureViewer.Interfaces. {. namespace JulMar.Windows.Interfaces. {. void Register( string key, Type winType); bool Unregister( string key); bool Show( string key, object state, bool setOwner, EventHandler. ShowDialog( string key, object state); }. }. In this post, we will look at the IUIVisualizer , and bring together some of the concepts we’ve talked about already through a new sample – a simple picture viewer: The application grabs all the images from the user’s photo folder and then displays each one onto the surface of a corkboard. par ?? par ?? par ??
Mark's Blog of Random Thoughts
- Friday, February 5, 2010
MVVM: Introducing the message visualizers
Now we can create a collection of the TitledCommand objects and display them to the user for execution. It returns a disposable object that you invoke Dispose on to return to the normal cursor. xmlns : ViewModels ="clr-namespace:ServicesTest.ViewModels". In this post, I will go over the simple message visualizers available in the MVVM Helpers toolkit. Essentially the idea is that it is fairly common to want to display a simple message from the ViewModel to the user. Displays a title + message to the user and allows them to dismiss it through a set of user-defined buttons.
Mark's Blog of Random Thoughts
- Monday, February 1, 2010
|
-
|
The Best from DevelopMentor
|
MORE
|
-
Sending your own objects to a WF4 workflow
To show how to do so I will replace the singe string with a person object. The CreateWorkflow() function will change now reflecting the fact that the service will no longer expect a string but a person object. DataContract(Namespace = "urn:WF4Sample:person" )]. MessageBodyMember(Namespace = "urn:WF4Sample:person" )]. MessageBodyMember(Namespace = "urn:WF4Sample:person" )]. MessageBodyMember(Namespace = "urn:WF4Sample:person" )]. MessageBodyMember(Namespace = "urn:WF4Sample:person" )]. DataMember].
The Problem Solver
- Thursday, August 20, 2009
-
Using Model – View – ViewModel with Silverlight
The complete model looks like this: 1: using System.ComponentModel; 2: 3: namespace SilverlightMVVMDemo.Model. Column ="1" /> 44: 45: The code behind is very simple and looks like this: 1: using System.Windows.Controls; 2: using SilverlightMVVMDemo.ViewModel; 3: 4: namespace SilverlightMVVMDemo.View. 13: 14: private void Button_Click( object sender, System.Windows.RoutedEventArgs e). 36: 37: void ModelPropertyChanged( object sender, PropertyChangedEventArgs e). View has only a single DataContext so you cannot bind it to multiple ViewModel objects.
The Problem Solver
- Tuesday, April 7, 2009
-
Exam objectives for 70-536 with links to MSDN
Microsoft 70-536 Objectives. Objectives as updated on Microsoft's Web site : March 29, 2007. system types (Refer System namespace ). Refer System.Collections namespace ). Refer System.Collections.Generic namespace ). Generic IComparable interface (Refer System Namespace ). Refer System.Collections.Specialized namespace ). Refer System namespace ). Refer System namespace ). Refer System.ServiceProcess namespace ). Refer System.Threading namespace ). IAsyncResult interface (Refer System namespace ). namespace ).
The Blomsma Code
- Monday, June 8, 2009
-
Getting started with Windows Workflow Foundation 4
Creating workflows is done by creating a WorkflowInstance object. This object is raises events for that workflow and only for that specific workflow. In fact the new Activity class is in a new assembly and namespace, the full name is System.Activities.Activity in the assembly System.Activities.dll. As you may have heard Windows Workflow Foundation 4 is not an upgrade from Windows Workflow Foundation 3 (or 3.5). The version numbers might suggest that the previous version was quite mature but in fact it refers to the version of the.NET framework. Well wrong actually!
The Problem Solver
- Monday, June 22, 2009
-
Using Windows Workflow Foundation 4 Receive from an non WF client
In our workflow the operation is named “Operation1” and our service contact name was “MyService” with the default namespace of “ [link] ”. Next up are the request and response objects. Namespace = "[link] , Name = "string" )]. Namespace = "[link] , Name = "string" )]. In a previous blog post I described how to use the WorkflowServiceHost and host a workflow with a Receive activity that waits for WCF messages. also added a WF4 client that called the service and received a response. interface MyService. {. OperationContract]. Enjoy!
The Problem Solver
- Wednesday, August 19, 2009
-
Marshalling native function pointers
To discuss this topic, consider the following simple API: namespace NativeAPI. {. The following code shows a delegate that can be mapped to the native function pointer of type PFNCallback : namespace ManagedWrapper { using namespace System::Runtime::InteropServices; [StructLayout(LayoutKind::Sequential)]. To wrap NativeAPI::SampleClass , you can implement the following wrapper class: namespace ManagedWrapper. {. namespace ManagedWrapper. {. NET objects are allocated on the GC heap which consists of. // pages with the PAGE_READWRITE flag. of the CLR.
Marcus' Blog
- Friday, April 6, 2007
-
Creating TFS Work Items programatically
The answer is quite simple: write a program that utilizes the Team Systems Object Model. 29: Console.WriteLine( "Adding new bug to Team Project {0}" , teamProject.Name); 30: 31: WorkItem wi = new WorkItem(witBug); 32: wi.Description = "This is a sample bug which was added through the object model" ; 33: wi.Reason = "New" ; 34: wi.Title = "You have Bugs! This is accomplished on line 14 by creating a new TeamFoundationServer object. One question I get a lot when teaching the VSTS course is "How can I move tasks or bugs from our existing system into TFS?". 10: class Program.
|
|
|