Note: Cross posted from Rituparna’s Blog.
Permalink
If you are using CodedUITest to test WPF applications then installing Windows Automation API 3.0 is a pre-requisite. Without this the virtualized controls in WPF wont be played back correctly and since lot of the WPF controls like ListBox/Datagrid are virtualized by default , this will lead to failures.
Windows automation API is pre-installed on WIN7 and can be installed on Vista/XP as well. This blog has all the details on howto get Windows Automation API 3.0 installed.
In case the machine does not have WAA3.0 code generated on doing action on WPF application will have the following comment
// An update for Windows Automation API 3.0 must be installed to enable automation on Windows Presentation Foundation controls. Please refer http://go.microsoft.com/fwlink/?LinkId=162159 for more information.
Similar comment is displayed in the MTLM UI for viewing recorded action as well.
This let’s the user know that the recording is not proper and user has to install WAA3.0 and re-record. Also a useful way to identify if the machine actually has Windows Automation API 3.0 installed
ciao
Whenever companies do something inexplicable, the nerd in me always comes back to that scene in Close Encounters of the Third Kind when Richard Dreyfus keeps building models of a mountain, culminating in a huge, muddy mess in his kitchen. Throughout it all he keeps saying “This means something.”
Well, the latest molehill into a mountain is the move by Time Inc. and Conde Nast, among others, to build a tablet-based interface for their flagship titles. This means something, but what it means is that the homes of Time and Gourmet (oh, wait), aren’t going to take the coming industrial disruption lying down.
Here is a really cool set of Visio Diagrams related to Microsoft SharePoint. The diagrams illustrate models, scenarios, and flowcharts for planning, designing and deploying SharePoint installations.
Models
Model: Business Intelligence
Model: Office SharePoint Server Application Security
Model: Office SharePoint Server Backup and Restore
Model: Office SharePoint Server Topologies
Model: Office SharePoint Server Baseline Site Hierarchies
Model: Office SharePoint Server Customization
Model: Office SharePoint Server Database Administration
Model: Office SharePoint Server Enterprise Content Management
Model: Office SharePoint Server Extranet Topologies
Model: Office SharePoint Server Inter-Farm Shared Services
Model: Office SharePoint Server Products Migration
Model: Office SharePoint Server Search Administration
Model: Office SharePoint Server Shared Services
Model: Upgrading Office SharePoint Server Products
Model: Upgrading SharePoint Portal Server 2003 to Office SharePoint Server (1 of 2)
Model: Upgrading SharePoint Portal Server Version 2 to Office SharePoint Server (2 of 2)
Scenarios
Scenario: Enterprise Content Management
Scenario: InfoPath Forms Services Customer Interaction Form
Scenario: InfoPath Forms Services Expense Reporting
Scenario: InfoPath Forms Services Insurance Claims
Scenario: InfoPath Forms Services Permits
Scenario: InfoPath Forms Services Supplier Survey
Scenario: Keeping Connections to Data Sources Current
Scenario: Large Corporate Internet Site (Infrequent Changes to Web Content)
Scenario: Office SharePoint Server Call Centre
Scenario: Office SharePoint Server Corporate Intranet Portal Site
Scenario: Office SharePoint Server Departmental Portal Site
Scenario: Office SharePoint Server Equities Research
Scenario: Office SharePoint Server Informational Portal Site
Scenario: Office SharePoint Server Out-Hosted Portal Sites (ASPs)
Scenario: Online News Internet Site (Frequent Web Content Updates and Searching)
Scenario: Preserving “One Version of the Truth” for Distributed Workbooks
Scenario: Records Management in Office SharePoint Server
Scenario: Rendering Data from Spreadsheets to Web Parts
Flowcharts
Office SharePoint Server Planning Flowchart, Part I (application administrators)
Office SharePoint Server Planning Flowchart, Part II (IT pros)
Office SharePoint Server Deployment Flowchart
This particular post has nothing to do with technology. I’m an avid college football fan and have always cheered for my alma mater, the Georgia Tech Yellow Jackets. Tonight, for the first time since I have been actively following them, we beat Clemson for the 2nd time this season (39-34) and earned a berth in the BCS Orange Bowl!!
Not to downplay Clemson, however, as they put up a really good fight both times and it came down to who had the ball last. The first game was equally amazing to watch and ended with a field goal to beat the Tigers 30-27. This game we won on a touchdown by Jonathan Dwyer! He’s the man! Speaking of the man, I think C. J. Spiller deserves to go to New York and be in the running for the Heisman. Amazing athlete who I’m sure will do well in the NFL.
Ok, I’m done gloating … hopefully this will earn the ACC more respect. Now on to the Orange Bowl!
One more thing .. of course I can’t leave Paul Johnson hanging high and dry in recognition. He has done an amazing job as head coach of GT, taking a team that went 7-5 to 9-4 and now 11-2 with a BCS berth, first appearance in the Orange Bowl since the early 60’s!
Since I want the transaction we’re creating to take the lock when created I also want to release the lock when the transaction is disposed: 1: public class When_using_a_transaction
2: {
3: class FakeLock : Lock
4: {
5: public bool IsLocked { get; private set; }
6:
7: public FakeLock()
8: {
9: IsLocked = false;
10: }
11:
12: public void Lock()
13: {
14: IsLocked = true;
15: }
16:
17: public void Unlock()
18: {
19:
Comments
are in Italics and marked as red.
bp main
– put a breakpoint at our main C++
function to allow the program execution to stop at that point. (P. 37)
uf
main – unassembled main function (P. 39)
.asm
no_code_bytes – suppresses the display of raw bytes (P. 40)
When the code is compiled in Release mode,
Visual C++ compiler is able to calculate the final result from the simple C
source code itself and generate code only necessary to update corresponding
memory locations. (P. 43)
In WinDbg and other debuggers, memory addresses
are displayed in hexadecimal
notation. (P. 50)
Binary
Decimal
Hexadecimal
0000
0
0
0001
1
1
0010
2
2
0011
3
3
0100
4
4
0101
5
5
0110
6
6
0111
7
7
1000
8
8
1001
9
9
1010
10
A
1011
11
B
1100
12
C
1101
13
D
1110
14
E
1111
15
F
(P. 51)
http://www.hanselminutes.com/default.aspx?showID=205
I can’t honestly say that I’ve ever been much of a patron of the dark arts. Mind you, a few years ago I was fascinated to see a chapter for a book on ADO.NET that I’d written come back from review with fifteen paragraphs about devil worship in the middle of it. I was about half way through editing this when I suddenly realized it sounded unfamiliar, and seemed to have little to do with asynchronous data access and stored procedures. I assume that the reviewer had got their Ctrl-somethings mixed up, and I still can’t help wondering if there is a Web site out there somewhere that has a detailed description of the behavior of a DataReader in the middle of an article about witchcraft and sorcery….(read more)
Related posts:Windows Azure Platform TCO/ROI Comparison ToolWindows Azure Platform TCO/ROI Analysis ToolMeasure TCO and ROI of your solution on Windows Azure
tweetmeme_url = ‘http://blogs.msdn.com/stevecla01/archive/2009/12/06/who-switched-the-internet-off.aspx’;
tweetmeme_source = ’stevecla’;
tweetmeme_service = ‘bit.ly’;
Related posts:Windows Azure Platform TCO/ROI Comparison ToolWindows Azure Platform TCO/ROI Analysis ToolMeasure TCO and ROI of your solution on Windows Azure
I’ve been meaning to throw together some thoughts on attached properties and how they can be used within the designer. Basically, you can think about attached properties as injecting some additional “stuff” onto an instance that you can use elsewhere in your code.
Motivation
In the designer, we want to be able to have behavior and view tied to interesting aspects of the data. For instance, we would like to have a view updated when an item becomes selected. In WPF, we bind the style based on the “isSelectionProperty.” Now, our data model doesn’t have any idea of selection, it’s something we’d like the view level to “inject” that idea on any model item so that a subsequent view could take advantage of. You can kind of view Attached Properties as a nice syntactic sugar to not have to keep a bunch of lookup lists around. As things like WPF bind to the object very well, and not so much a lookup list, this ends up being an interesting model.
To be clear, you could write a number of value converters that take the item being bound, look up in a lookup list somewhere, and return the result that will be used. The problem we found is that we were doing this in a bunch of places, and we really wanted to have clean binding statements inside our WPF XAML, rather than hiding a bunch of logic in the converters.
How Does it Work
First, some types.
Name
Description
AttachedPropertiesService
Service in editing context for managing AttachedProperties
AttachedProperty
Base attached property type (abstract)
AttachedProperty<T>
Strongly typed attached property with interesting getter/setter programmability
in diagram form:
One thing that might look a little funny to some folks who have used attached properties in other contexts (WF3, WPF, XAML), is the “IsBrowsable” property. The documentation is a little sparse right now, but what this
