.NET

Job Opening in Richardson, TX: Engineering Test Developer

Adam Sills — Thu, 05 Oct 2006 18:52:00 GMT

Standard stuff (pulled off our website):

Candidate must be highly motivated, innovative and able to work independently. Applicant must be able to communicate effectively and work well in a high performance, fast paced, team environment. Applicants will be tasked with Testing our Software Development Kit, .NET API's, interfaces and class templates for our RFID and Sensor Platform. Candidates will also be testing application user interfaces and may be assisting Technical Support with second level technical support calls as needed. A qualified candidate must have been part of a complete Quality Assurance effort within the total development life cycle and must have broad experience in testing components which run under Windows Services. Responsibilities will include writing test cases, developing test scripts, testing API's and SDK's. Degree in Computer Science or related technical field is preferred.

Required Skills:
* Experience in software life cycle testing methodologies
* Software Test Life Cycle and Development Life Cycle
* OOP, Windows Development
* Software development experience with Microsoft development tools & methodologies including the .NET Framework & C#.
* Background in object based or object oriented programming
* Experience in the use of XML, Web Services, RDBMS interfaces
* Worked on a high performance team in a high-tech startup or startup-like environment.

Additional Skills:
* Specification documentation (UML, State/ Transition Diagramming, Dataflow Diagramming, Use case documentation)
* Enterprise integration methods and tools (e.g. connecting to large ERP, SCM, CRM, WMS, legacy backend data processing subsystems)
* Microsoft MOM, SMS, Biztalk, MSMQ, IIS
* RFID & sensors
* VB.NET, Windows CE / Pocket PC Development, Compact Framework
* Test automation tools (Seque in particular)
* Handheld & Portable device usage using Windows CE, PPC OS & .NET Compact Framework
* Wireless LAN/WAN knowledge & experience

Company information:
GlobeRanger Corporation
Careers page:
http://www.globeranger.com/company/careers.asp

Please submit your resume in confidence to careers@Globeranger.com

Job Opening in Richardson, TX: Software Engineer

Adam Sills — Thu, 05 Oct 2006 16:40:00 GMT

Standard stuff (pulled off our website):

We are looking for a software engineer to join our world-class product development team, which is responsible for the architecture, design and development of GlobeRanger's flagship product, iMotion. This position requires a creative, passionate, and technically strong individual that excels in challenging projects and team environments.

* Five or more years experience developing object oriented products and solutions
* Two or more years of experience developing in C# and .Net
* Excellent verbal and written communication skills
* Must enjoy collaborating and working with team members
* BSEE, BSCS or equivalent experience

Company information:
GlobeRanger Corporation
Careers page:
http://www.globeranger.com/company/careers.asp

Want to apply:
Send email with resume to careers@globeranger.com

Unusual IE7b3 bug: SYSTEM applications cannot start programs using Process.Start (part 2)

Adam Sills — Mon, 18 Sep 2006 18:43:00 GMT

Since I originally posted this in July, I've gotten absolutely nowhere with Microsoft. I have, however, had a couple hundred google searches for things like “IE7 beta process.start error“. Since then my bug was closed, someone else reopened it, and I've found another similar bug where the IE7 beta and RC take over shell execute and deny programs from being launched.

Luckily for me, our workaround was to simply not use the shell (ShellExecute=false) but that definitely isn't an option for everyone.

UPDATE (9/7/2006):
Microsoft closed my bug without really looking at it. I got “not an IE problem“. Luckily, someone else has picked up the cause and resubmitted with a bit more information for me. If you are having this problem and want it fixed (because ShellExecute=false may not work for you), then go here and vote/validate the bug:
https://connect.microsoft.com/IE/feedback/ViewFeedback.aspx?FeedbackID=180644

UPDATE 2 (9/18/2006):
Microsoft closed the new bug again without really looking at it. “Please see if it happens in Beta 3“ they said. Today I found another variation of what appears to be the same bug.
https://connect.microsoft.com/IE/feedback/viewfeedback.aspx?FeedbackID=202102

Their product feedback process is really a pain. And you can't call product support services on a beta product so you're stuck submitting feedback through a system where feedback gets ignored. GAH.

ORIGINAL:
So I've come across a real interesting side-effect of the IE7 Beta 3 install. A program running as SYSTEM under .NET 1.1 (either as a Windows service or as a scheduled task) cannot start a process using the Process.Start method. It fails with a Win32Exception (”Access is denied”).

A SYSTEM program gets an access denied error? That's an awfully strange effect of a browser update, don't you think? To get this sample program to run as SYSTEM, create a scheduled task and specify SYSTEM as the username (and don't enter a password). Then just right-click the scheduled task and select Execute.

Here's the simple code that fails when run under SYSTEM:

using System;

using System.Diagnostics;

using System.IO;

namespace NetUserIE7Tester {

class Class1 {

[STAThread]

static void Main(string[] args) {

StreamWriter writer = new StreamWriter( "C:\\ie7netusertest.log", false, System.Text.Encoding.UTF8 );

ProcessStartInfo info;

try {

info = new ProcessStartInfo(Environment.SystemDirectory + "\\ipconfig.exe",

"/all");

info.WindowStyle = ProcessWindowStyle.Hidden;

Process.Start(info).WaitForExit();

}

catch( Exception ex ) {

writer.WriteLine( "Exception trying to IPconfig: " + ex.ToString() );

}

writer.WriteLine( "Finished" );

writer.Close();

}

Note that this is just sample code. It doesn't have to be IPCONFIG.exe, it can be ANY executable (in the case of my program, I'm using one of the NET.exe commands). If you run this program under any other user account (an account that can actually be logged in with) it executes perfectly.

If you're feeling frisky and want to try it out and it breaks on your IE7 Beta 3 install also (Windows XP, .NET 1.1, I haven't tried it on anything else), could you go to this IE7 bug and indicate that you can reproduce it?

https://connect.microsoft.com/IE/feedback/ViewFeedback.aspx?FeedbackID=152600

Unusual IE7b3 bug: SYSTEM applications cannot start programs using Process.Start

Adam Sills — Mon, 03 Jul 2006 12:54:00 GMT

Here's the simple code that fails when run under SYSTEM:

using System;

using System.Diagnostics;

using System.IO;

namespace NetUserIE7Tester {

class Class1 {

[STAThread]

static void Main(string[] args) {

StreamWriter writer = new StreamWriter( "C:\\ie7netusertest.log", false, System.Text.Encoding.UTF8 );

ProcessStartInfo info;

try {

info = new ProcessStartInfo(Environment.SystemDirectory + "\\ipconfig.exe",

"/all");

info.WindowStyle = ProcessWindowStyle.Hidden;

Process.Start(info).WaitForExit();

}

catch( Exception ex ) {

writer.WriteLine( "Exception trying to IPconfig: " + ex.ToString() );

}

writer.WriteLine( "Finished" );

writer.Close();

}

https://connect.microsoft.com/IE/feedback/ViewFeedback.aspx?FeedbackID=152600

iMotion Edgeware Platform 5.2: Workflow Service Providers

Adam Sills — Fri, 30 Jun 2006 17:57:00 GMT

A link between event controls in the iMotion Edgeware Platform represents the flow of data in the form of an event and delivered through a method invocation and is the primary way for event controls to “talk” to each other. This in-band communication may not always be the most appropriate way for one event control to execute another event control and an out-of-band method of communication may be more appropriate. ... (more) ...

You just knew it had to be coming: ASP.NET project in VS2005 is back

Adam Sills — Thu, 08 Dec 2005 13:35:00 GMT

Scott Guthrie is posting that they're developing a new project type for ASP.NET projects in Visual Studio 2005. I still have no idea why that crackpot (note, "crackpot" is meant to be funny) thought that removing the concept of a project from ASP.NET would sit well with people who had been creating ASP.NET applications for four or more years (with another year for betas).

Enough people have complained publicly about it (I have, though not very vocally) that they're putting it back in. And I don't buy the crap that it's mostly for project upgrading from VS2003. It has nothing to do with upgrading projects. It has everything to do with pulling the rug out from everyone's feet and only some people don't mind.