Note: Cross posted from Rubel’s Blog.
Permalink
As I had mentioned in my earlier posts that you can enable a number of Diagnostic Data Adapters in test setting so as to collect various types of data while running tests in Test Runner. Sometimes it is confusing if you don’t get any log from a diagnostic data adapter though you’ve enabled it in test setting. There can be many reasons for this behavior like data collector is not expected to generate log in that particular scenario, data collector pre-reqs are not met successfully, that particular data collector is not expected to generate log at all e.g Network Emulation. This post intends to explain various reasons for log generation failure from each data diagnostic adapter. This is NOT an advanced guide for troubleshooting all data diagnostic adapters’ warnings / errors but you can quickly refer to it if you are not seeing logs from a data diagnostic adapter.
IntelliTrace and Test Impact
Both IntelliTrace and Trace Impact data collectors have a number of pre-reqs:
1) They work only for applications written with managed code
2) AuT process need to be started after launching the Test Runner as they needs to instrument modules, binaries or executables that are loaded into a process.
3) ASP .NET Client Proxy for IntelliTrace and Test Impact needs to be enabled in test setting for client role while collecting test data from ASP. NET applications hosted on remote boxes.
4) Computer’s IP address / hostname need to be used instead of “127.0.0.1” “local host” while collecting data from locally hosted ASP.NET apps e.g. please use http://microsof-7f734b/webapplication1/default.aspx instead of http://localhost/webapplication1/default.aspx
5) AuT Process / required modules are included for data collection in configuration settings of collectors. Please check articles mentioned below for details on configuring IntelliTrace and Test Impact:
a. Configuring IntelliTrace
b. Configuring Test Impact
So if
El tema alrededor del manifiesto se va desarrollando, hay mucha más gente que ha escrito a raíz de los sucesos acaecidos la semana pasada, y parece que va habiendo gente que de manera razonable aporta puntos de vista distintos.
De cualquier manera, a mi me va pareciendo que el tema de fondo que lo va empapando todo es el debate sobre la propiedad intelectual y sobre las normas de juego alrededor de los derechos de uso y de copia.
Voy enlazando aquí algunos, que me parecen en general informados, suficientemente desapasionados y bastante razonables. Cada una de su padre y de su madre, eso sí:
Empezamos con un poco de humor gráfico: Eduangi.com
Vida de un consultor: Manifiestos, churras y merinas
Barcepundit
Materias grises: paranoia, piratería y libertades
Geografía subjetiva: Sobre el manifiesto
Industria Audiovisual: Revueltas en el aire digital, una sociedad perpleja a la que se le ha hurtado el verdadero debate
Medios en la red: Razones por las que este blog no se ha adherido al manifiesto
Eudald Domenech: ¿Pirata yo?
Más:
Jesteban.net: Porqué NO apoyo “El Manifiesto por los derechos de Internet”
As we all know there is a limitation in URL length as 260 characters for many reason and there are many articles from different specialties talks about it.
Recently I have come across a scenario where users are able to upload documents to the document library and sub folders, if we calculate the total URL length of the uploaded document, it is more than 260 characters, SharePoint didn’t throw any error or warning message while uploading documents to the folders.
When users are trying to edit the same document by clicking on document link or edit using Microsoft Office Word in dropdown menu, we get below warning messages.
"The URL for this file is too long for the application. A temporary copy of this file will be opened on
your computer. You must save this copy as a new file"
The document will be opened in Read Only mode and when we try to save the document back to same location we get
"This file is read-only."
"The document could not be opened for editing. A Windows SharePoint Services compatible
application could not be found to edit the document."
Q1. Does SharePoint has 260 characters limit?
Answer: Yes, it has the limit.
Q2. If SharePoint has 260 characters limit then does it throw any error/warning while uploading documents?
Answer: Yes, it does throw warning message and terminate the upload process.
Q3. As mentioned SharePoint has 260 limit and it does not allow users to upload, then in what situation we get into the above issue (able to upload but not able to edit).
Answer: As I have mentioned SharePoint has 260 characters restriction for both operations upload and edit. Sometimes users are experiencing issue only edit not while uploading.
Here is the explanation how restriction applied while uploading and editing.
For example my
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
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!
My friends at Interknowlogy are in need of developers – Silverlight and WPF – immediately! This is the company owned by Tim Huckaby, who has led some great work there. They are a Microsoft Partner company, and are well connected. (Just go find the picture at the Windows Vista launch with Tim standing with Ballmer.) Anyway, their COO, Emilie Hersh, sent me the following:
If you know any good people – PLEASE send them my way! I do not necessarily care where they live. We will attach them to existing teams so that they get to work with our people and augment delivery. A more comfortable start, I think!
Ideally we can contract to start – definitely interested in contract-to-hire. I believe there are some great people out there interested in the cool projects we do!
Send your resume to findyourcalling@interknowlogy.com to get your conversation started.
A colleague of mine Jon Box talked about the interesting aspects of IE8 that can be leveraged by web sites for pushing their brand. The podcast can be found at : Episode 41: Developing Better User Experiences with Internet Explorer 8 with Jon Box.
Jon also blogged about this at http://blogs.msdn.com/jonbox/archive/2009/12/05/check-out-my-interview-on-deep-fried-bytes.aspx.
- Hanu
On Wednesday, a mere hour or so after the end of Day 1 of TechDays Montreal, came Career Demo Camp Montreal, a community event that combined presentations on job-hunting and career-building with demos of projects by Montreal-area developers.
What’s With All These “Demo” and “Camp” Events and Techdays?
For this year’s edition of TechDays, we decided to try something new. TechDays is a two-day cross-Canada conference taking place in seven cities – Vancouver, Toronto, Halifax, Calgary, Montreal, Ottawa and Winnipeg – and all the conference events take place during the day. There are no events scheduled for after 5 p.m., which means that on the evening of Day 1, the venues are ours – and unused. Since they’re already set up for presentations and it costs relatively nothing to hire an A/V tech for a few extra hours, we decided to make our venues open to local developer community events. We even lent a hand in helping put the events together.
This year, we opened our space to four such community events:
Demo Ignite Camp in Vancouver with the help of Boris Mann
FailCamp Toronto 3 in Toronto with the help of Justin Kozuch (Refresh Events) and Meghann Millard (Unspace)
Career Demo Camp Montreal with the help of Jean-Luc SansCartier (iWeb) and Yann Larrivee (PHPQuebec/Confoo)
…and next week’s Demo Night in Canada in Ottawa with the help of Colin Melia (Ottawa .NET Community) and Scott Lake (Startup Ottawa)
The Career Portion
People started milling in at around 6:00 p.m.:
The evening began with Alex Kovalenko, Director of Operations at the tech recruiting company Kovasys. His presentation was all about what smart job hunters do, how to write a good tech resume, and the elements of a successful tech interview.
Alex was joined by a couple of his coworkers at Kovasys for the Q&A session, which
UI Automation — Under the Hood (1)
The desktop development technology revolved from Win32 SDK, .NET WinForm to WPF and Silverlight. The relative UI Automation testing technology changes as well.
This doc describes UI Automation technology on Windows platform in two parts. The first part introduces the technology revolution. The second part addresses the lasted UIA in detail.
Part1: The revolution of UI Automation technology
UI Automation refers controlling a UI application form another application by simulating user actions. Usually UI Automation involves the following three parts:
· Probing the source
It refers the process to identify target UI element. For example, to test calc.exe (calculator), the first step is to distinguish the calculator window from other window like notepad. To continue test the menu, it requires identification of the location of menu bar, and obtaining the second level of menu item. In other words, the basic step is to navigate the UI tree, from root desktop to the sub-controls, until the target UI element is identified.
· Simulating user action
It refers simulating user input, like mouse, keyboard and touch screen. It may involve simulating IME input, combination input or user habit like input speed.
· Checking the UI property and behavior
It refers validating UI element property, like window title, listbox elements, status of checkbox.
Win32 SDK and Windows Message
Before CLR there are merely two techs for UI development: Win32 SDK or DirectX. As DirectX is mainly targeting on special field like game and CAD, I will not include it here.
No matter MFC, VCL or VB6 is used, Win32 SDK is the core. The UI element through the development life cycle is always HWND and Windows Message. There are only three parts: Win32 API, Windows Message and Windows Hook.
Usually the test client use FindWindowEx and EnumWindow to iterate window and sub control, until the testing target is identified. It sends/posts
[...]
