Friday, January 23, 2009

Partner and ISV Solutions for Microsoft Dynamics GP

 

Partner and ISV Solutions for Microsoft Dynamics GP

I can't count on a weekly basis how many e-mails I get asking me about an ISV Solution for Dynamics GP. I sometimes reference Solution Finder but as we all know Solution Finder does not always return the results we expect. Well I am happy to announce that we have exported all the ISV's into a Excel Spreadsheet that you can pivot on. I can personally tell you that I was excited to finally see this.

Here is a link on PartnerSource where you can download the spreadsheet: ISV List

Published Friday, January 23, 2009 2:52 PM by jeffk

US Microsoft Dynamics GP Field Team : Partner and ISV Solutions for Microsoft Dynamics GP

SharePoint, Business Process & Forms

 

SharePoint, Business Process & Forms

Here's a little screencast I've recorded showing a demonstration of some of the Microsoft Office SharePoint Server Forms Services capabilities together with InfoPath forms rendered through a browser and also including simple workflow creation and deployment through SharePoint Designer.

Microsoft%20Office%20SharePoint%20Server%20-%20Business%20Process%20%26%20Forms
Microsoft Office SharePoint Server - Business Process & Forms

Based on the Demo Showcase virtual images, a resource readily available to Microsoft Gold and Certified partners, the demo lasts just a touch over ten minutes, I'd love to know what you think of it!

Parkesy

Posted: Friday, January 23, 2009 12:27 PM by chrisp

Chris Parkes: A PC is not just for Christmas... : SharePoint, Business Process & Forms

Thursday, January 22, 2009

Links to standalone .NET Framework 2.0 SP2 core and language pack installer packages

 

Links to standalone .NET Framework 2.0 SP2 core and language pack installer packages

The .NET Framework 3.5 SP1 was released last fall along with Visual Studio 2008 SP1.  The .NET Framework 3.5 SP1 installs the .NET Framework 2.0 SP2 and the .NET Framework 3.0 SP2 behind the scenes as prerequisites.  Initially, the only way to get the .NET Framework 2.0 SP2 was to install the full .NET Framework 3.5 SP1 package.

Last week, a standalone installer package for the .NET Framework 2.0 SP2 was posted on the Microsoft Download Center.  There are x86, x64 and ia64 versions of this package, and the package allows you to install the .NET Framework 2.0 SP2 on Windows 2000, Windows XP and Windows Server 2003 without needing to install any .NET Framework 3.0 or 3.5 packages.

Note that there is not a standalone package for the .NET Framework 2.0 SP2 for Windows Vista or Windows Server 2008.  In order to install the .NET Framework 2.0 SP2 on those operating systems, you will still have to install the .NET Framework 3.5 SP1.

Here are links to download locations for the .NET Framework 2.0 SP2:

For the language packs, you will need to go to the above link and change the language drop-down to the language that you want to download the language pack for, then download the files listed in the language-specific version of the download page.

Published Thursday, January 22, 2009 8:34 PM by astebner

Aaron Stebner's WebLog : Links to standalone .NET Framework 2.0 SP2 core and language pack installer packages

Finding out how to call an existing Report

 

Finding out how to call an existing Report

David Meego

Over the years, I have been asked many times how to call a Report Writer report to make it behave the same as if it was called by the original code.

If you are member of the Source Code program, you could always find the run report command in the source script and that would provide the information about the Restrictions or Legends passed.  However, this information can be obtained without needing access to the source code.

The Dexterity Report Writer has a debugging feature which we can leverage to obtain the information we need.  There are two methods of activating the DebugRW functionality:

  1. Use the Support Debugging Tool, Tools >> Support Debugging Tool >> Options >> Dex.ini Settings >> Reports.  Mark the "Logs the run report statement as the Report Writer sees it" checkbox.
  2. Manually add DebugRW=2 setting to the DEX.INI file.

Once active, every time the Report Writer runs a report it will append to the DebugRW.txt file the details of how the report was called. 

Below is the information logged for when the 'RM Customer Report' was printed from the Customer Maintenance window for customer "Aaron Fitz Electrical":

rw_init();

run report 'RM Customer Report' (256)
legends "        Current",
  "   31 - 60 Days",
  "   61 - 90 Days",
  "  91 - 120 Days",
  "AARONFIT0001 - AARONFIT0001",
  "Aaron Fitz Electrical - Aaron Fitz Electrical",
  "USA-ILMO-T1 - USA-ILMO-T1",
  "Retail - Retail",
  "PAUL W. - PAUL W.",
  "TERRITORY 1 - TERRITORY 1",
  "Aaron Fitz Elec - Aaron Fitz Elec",
  "98052-6399 - 98052-6399",
  "WA - WA",
  "42555501010000 - 42555501010000",
  "Bob Fitz - Bob Fitz",
  "by Debtor ID",
  "Type:",
  "User-Defined 2:",
  "Registration"
( RM_Customer_MSTR(141).Customer Number(493) = "\012AARONFIT0001   " ) report queued with result = 1

rw_term();

NOTE: The Resource ID information in brackets for the report, table and fields.  You can use the Resource Information window in the Support Debugging Tool to cross reference resources by their ID.  This is sometimes useful when the name of the resource is not shown correctly and displays '[Not Found]'.

The Restriction is shown in the Table.Field format and will need to be converted to the Field of table Table format for the actual Dexterity call.  The Legends will probably need a little analysis to identify what information is being passed to the report.  You might need to change options and print the report again to see what changes the options can make to the legends.  Once you have the legends identified you can then place the values into the string fields to pass to the report.

Based on the information captured, you will be able to generate a run report command similar to one below:

Example Report Writer Call

run report 'RM Customer Report' with restriction
'Customer Number' of file RM_Customer_MSTR = 'Customer Number'
legends
l_legend1, l_legend2, l_legend3, l_legend4,l_legend5,
l_legend6, l_legend7, l_legend8, l_legend9, l_legend10,
l_legend11, l_legend12, l_legend13, l_legend14, l_legend15,
l_legend16, l_legend17, l_legend18, l_legend19;

As you can see this technique can be used to help a developer understand how they can call existing reports.

David

Posted: Friday, January 23, 2009 10:30 AM by David Musgrave

Developing for Dynamics GP : Finding out how to call an existing Report

Introducing BITS PowerShell Cmdlets!

 

Introducing BITS PowerShell Cmdlets!

Published 23 January 09 01:40 AM | wmfblog

The BITS (Background Intelligent Transfer Service) team is happy to announce the release of BITS PowerShell cmdlets in the Windows 7 beta! BITS PowerShell cmdlets combine the richness and usability of PowerShell scripting with the network-awareness and persistence of BITS file transfers. We believe that the addition of BITS cmdlets will make it easier for admins to manage and automate file transfer tasks by providing the following benefits.

For PowerShell admins considering BITS:

· Politeness: File transfers can be conducted in the background to preserve the responsiveness of other network apps

· Fire-and-forget persistence: BITS automatically tries to resume transfers that have been interrupted by temporary hiccups such as network disconnections or system reboots

For BITS API and BITSAdmin considering the switch to PowerShell cmdlets:

· Admin-Focused: Automate file transfers tasks in an extensible and management-oriented scripting language

· Usability: Consistent syntax across PowerShell cmdlets makes PowerShell scripting easy to learn and use

A primer on BITS can be found at http://msdn.microsoft.com/en-us/library/aa362708(VS.85).aspx.

On your mark…

Before using the BITS cmdlets, they must be loaded using the following cmdlet.

Import-Module FileTransfer

This cmdlet needs to be called whenever a new PowerShell session is started. This step can be avoided by adding the above cmdlet to your profile script. The location of this script is given by the $profile variable. Once this has been added to the profile script, the BITS cmdlets are loaded whenever a new PowerShell session is started.

Get set…

Discovering and navigating through all of the BITS PowerShell cmdlets can be a daunting task. A good place to start is by running the following cmdlet, which lists all of the BITS PowerShell cmdlets.

Get-Command –Module FileTransfer

Without further ado, here are the BITS cmdlets in a nutshell… or PowerShell.

Start Your Engines

New-FileTransfer

Creates a BITS job to transfer one or more files between two locations. By default, this cmdlet operates in synchronous mode and returns when all files have been transferred. A file transfer done in this mode is similar to a simple copy command. Managing file transfer tasks is not supported in this mode since it blocks until all files have been transferred.

The New-FileTransfer cmdlet can also operate in asynchronous mode, where it returns a BITS job object immediately. Think of this mode as the starting point for managing file transfers tasks. In general, a BITS job should be created asynchronously before passing it as a parameter to the other BITS cmdlets .

(Note: It is possible to modify synchronously created BITS jobs from a different PowerShell session using BITS cmdlets or from a CMD prompt using the BITSAdmin tool. This is not recommended, since it is much simpler to just modify BITS jobs created using the asynchronous mode.)

Meet Your Pit Crew

Add-FileTransfer

Adds one or more files to a BITS job.

Get-FileTransfer

Retrieves a list of BITS jobs for the current user. This cmdlet is handy for piping a list of BITS jobs into another cmdlet. For example, you can pipe this into the Clear-FileTransfer cmdlet to cancel all BITS jobs.

Set-FileTransfer

Modifies the properties of a BITS job. This is handy for changing BITS job properties on the fly, such as changing the aggressiveness of a BITS job.

Suspend-FileTransfer

Suspends a BITS job. This cmdlet pauses a BITS job’s file transfers until the BITS job is resumed by the Resume-FileTransfer cmdlet.

Resume-FileTransfer

Resumes a BITS job. Calling this cmdlet will resume a suspended BITS job and start file transfers from where they left off.

Complete-FileTransfer

Completes and removes a BITS job. Using this cmdlet will save any transferred files and remove the BITS job.

Clear-FileTransfer

Cancels and removes a BITS job. This is similar to Complete-FileTransfer with one exception. Files that are part of the BITS job will not be saved, even if they have been transferred.

Go!!

Give the BITS cmdlets a test drive and explore how they can be used to satisfy your file transfer needs. Keep reading in the future for some examples and ideas on using BITS cmdlets!

Lost, Need Directions?

For examples and documentation on how to use each cmdlet, try looking at the cmdlet help.

Get-Help <Cmdlet Name>

For more information about BITS, check out the following link:

http://msdn.microsoft.com/en-us/library/bb968799(VS.85).aspx

Alex Ng [MSFT]

Windows Management Infrastructure Blog : Introducing BITS PowerShell Cmdlets!

New Office Words for 2009

 

New Office Words for 2009

BLAMESTORMING.

Sitting round in a group, discussing why a deadline was missed or a Project failed, and who was responsible.

SEAGULL MANAGER.

A manager, who flies in, makes a lot of noise, craps on everything, and then leaves.

TESTICULATING.

Waving your arms around and talking bollocks. 

SALMON DAY.

The experience of spending an entire day swimming upstream only to get screwed and die.

CUBE FARM.

An office filled with cubicles.

PRAIRIE DOGGING.

When someone yells or drops something loudly in a cube farm, and people's heads pop up over the walls to see what's going on. (This also applies to applause for a promotion because there may be cake.)

SITCOMs.

Single Income, Two Children, And Oppressive Mortgage. What yuppies turn into when they have children and one of them stops working to stay home with the kids or start a 'home business'.

SINBAD.

Single working girls. Single income, no boyfriend and desperate.

PERCUSSIVE MAINTENANCE.

The fine art of whacking the crap out of an electronic device to get it to work again.

ADMINISPHERE.

The rarefied organisational layers beginning just above the rank and file. Decisions that fall from the 'adminisphere' are often profoundly inappropriate or irrelevant to the problems they were designed to solve.

404.

Someone who's clueless. From the World Wide Web error message '404 not found' meaning that the requested document could not be located.

OH - NO SECOND.

That minuscule fraction of time in which you realize that you've just made a BIG mistake (e.g. you've hit 'reply all').

Published 22 January 09 09:23 by pdestoop

Architects Rule! : New Office Words for 2009

Wednesday, January 21, 2009

Application Patterns for Application Architecture

 

Application Patterns for Application Architecture

We created an initial set of Application Patterns as part of our patterns & practices Application Architecture Guide 2.0 project.   The purpose of the application patterns is to show a skeletal solution for common end-to-end applications.  Each application pattern includes a scenario, a pattern solution, and a technical solution.  This provides you with a relatively stable backdrop and starting point to reuse lessons learned from successful applications.

Application Patterns
Here's our initial set of application patterns:

Example Application Pattern
The heart of each application pattern revolves around the scenario, the pattern overlay, and the technology overlay:

Scenario
Here's the backdrop we use for the baseline architecture:

Scenario

Pattern Solution
Here's our pattern overlay:

PatternsSolution (2)

Tech Solution
Here's our technology overlay:

TechnologySolution (2)

Application Pattern Template
Here's the core structure of each application pattern:

Section
Description

Key Characteristics
Identifies the distinctions that impact the application architecture and design. Helps you quickly identify whether the scenario is relevant for your situation.

Scenario
A brief illustration of the deployment scenario and main application parts.

Key Characteristics
Identifies the distinctions that impact the application architecture and design. Helps you quickly identify whether the scenario is relevant for your situation.

Pattern Solution
Provides an overaly of patterns on top of the key application parts.

Pattern Solution Details
Elaborates on the patterns. Includes pattern summaries and any relevant example information.

Technical Solution
Provides an example overlay of technologies.

Technical Solution Details
Elaborates on the technologies. Includes technology summaries and any relevant example information, such as code snippets or psuedocode.

Additional Resources
Provides a set of directly relevant resources where you can find more information.

Feedback

  1. What are 3 things you like about the approach?
  2. What are 3 things you would improve?

My Related Posts

Published 21 January 09 08:33 by J.D. Meier

J.D. Meier's Blog : Application Patterns for Application Architecture

Blog Archive