{"id":2516,"date":"2010-11-22T10:55:18","date_gmt":"2010-11-22T18:55:18","guid":{"rendered":"http:\/\/www.sapien.com\/blog\/?p=2516"},"modified":"2010-11-22T10:55:36","modified_gmt":"2010-11-22T18:55:36","slug":"feature-peek-2011-bridging-the-gap-part-1","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2010\/11\/22\/feature-peek-2011-bridging-the-gap-part-1\/","title":{"rendered":"Feature Peek 2011: Bridging the gap, Part 1"},"content":{"rendered":"

The question about a 64 bit version of PrimalScript has been raised a few times in our support forum. The question was, however, not really about what platform PrimalScript uses, but what platform the scripts run on.<\/p>\n

As software transitions from 32 to 64 bit you need a development environment that works on BOTH sides, not exclusively on either side. Many administrators are tasked with supporting legacy 32 bit software and bleeding edge 64 bit server components, some even on the same machine.<\/p>\n

PrimalScript 2011 will do just that, work on both sides, indifferent to its own “bitness”.<\/p>\n

\"PowerShell<\/a><\/p>\n

A little selector in the script toolbar lets you select in which environment to run your script. The sample above runs a PowerShell script in 32 bit mode.
Below you see the same script executed in 64 bit mode.<\/p>\n

\"PowerShell<\/a><\/p>\n

If you look closely you see that the output of the Processor_Architecture variable shows the corresponding value.<\/p>\n

Aside from the toolbar you can also use a menu topic to change between platforms:<\/p>\n

\"Menu<\/p>\n

Do you have to set that every time you need to change where script runs? We will visit that next time in Part 2. Stay tuned.<\/p>\n","protected":false},"excerpt":{"rendered":"

The question about a 64 bit version of PrimalScript has been raised a few times in our support forum. The question was, however, not really about what platform PrimalScript uses, but what platform the scripts run on. As software transitions from 32 to 64 bit you need a development environment that works on BOTH sides, […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[582,176,21,25],"tags":[564,526,525,615,28,37],"class_list":["post-2516","post","type-post","status-publish","format-standard","hentry","category-feature-peek","category-sneak-peeks-at-the-next-version-of-primalscript","category-software-news","category-windows-powershell","tag-564","tag-32-bit","tag-64-bit","tag-platform","tag-powershell","tag-primalscript"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t