<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.esri.com/Dev/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>VBA and VB6 with ArcGIS: What's the Story?</title><link>http://blogs.esri.com/Dev/blogs/arcobjectsdevelopment/archive/2009/03/30/VBA-and-VB6_3A00_-The-Road-Ahead.aspx</link><description>Coming out of the ESRI Developer Summit last week, and hearing some buzz about this on Twitter, we figured it would be a good time to catch everyone up with the ArcGIS support story for Visual Basic 6 (VB6) and Visual Basic for Applications (VBA). We</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Debug Build: 61120.2)</generator><item><title>re: VBA and VB6 with ArcGIS: What's the Story?</title><link>http://blogs.esri.com/Dev/blogs/arcobjectsdevelopment/archive/2009/03/30/VBA-and-VB6_3A00_-The-Road-Ahead.aspx#4412</link><pubDate>Tue, 31 Mar 2009 21:31:01 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:4412</guid><dc:creator>theavey</dc:creator><description>&lt;p&gt;After DevSummit it sounds like ESRI is going to replace the VBA scripting environment with Python. The only problem with this is the inability to cut VBA code into VB6 solutions when you want to move a prototype to a more robust environment. &lt;/p&gt;
&lt;p&gt;Will there be a scripting / prototpying environment that will be as seamless as the VBA/VB6 environments?&lt;/p&gt;
</description></item><item><title>re: VBA and VB6 with ArcGIS: What's the Story?</title><link>http://blogs.esri.com/Dev/blogs/arcobjectsdevelopment/archive/2009/03/30/VBA-and-VB6_3A00_-The-Road-Ahead.aspx#4597</link><pubDate>Mon, 06 Apr 2009 18:25:16 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:4597</guid><dc:creator>scott bridwell</dc:creator><description>What will happen with the vb script components embedded in various pieces of ArcGIS such as the field calculator and label rendering? Will these features exist for the foreseeable future or will a new scripting framework replace it?</description></item><item><title>re: VBA and VB6 with ArcGIS: What's the Story?</title><link>http://blogs.esri.com/Dev/blogs/arcobjectsdevelopment/archive/2009/03/30/VBA-and-VB6_3A00_-The-Road-Ahead.aspx#4617</link><pubDate>Tue, 07 Apr 2009 02:02:38 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:4617</guid><dc:creator>Simon </dc:creator><description>I assume this has come around more because MS are discontinuing VBA &amp; VB6?

http://msdn.microsoft.com/en-us/isv/bb190538.aspx

Its good that ESRI appear to be enhancing python support at 9.4 - However, I imagine a number of users are not keen on using Visual Studio, and prefer to customise the mxd's themselves as opposed to creating .DLL files.  </description></item><item><title>re: VBA and VB6 with ArcGIS: What's the Story?</title><link>http://blogs.esri.com/Dev/blogs/arcobjectsdevelopment/archive/2009/03/30/VBA-and-VB6_3A00_-The-Road-Ahead.aspx#4762</link><pubDate>Thu, 09 Apr 2009 23:04:13 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:4762</guid><dc:creator>alaframboise</dc:creator><description>&lt;p&gt;Sorry for the delay folks. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Scott: As with all releases, we are working hard to maintain all aspects of backwards compatibility with the 9.4 release. &amp;nbsp;Features such as VB scripting will still be supported but we will be considering alternative methods to scripting as we move forward.&lt;/p&gt;
&lt;p&gt;Simon: As technology evolves, we evolve as well. &amp;nbsp;When a development environment is no longer supported by a vendor, it makes it very difficult for us to build and design future versions of our software on those technologies. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;And to your second point, there are definitely advantages and disadvantages to writing code in the application tier vs in DLLs. &amp;nbsp;One thing to keep in mind however is that writing pure .NET DLLs is considerably easier than writing and deploying traditional COM DLLs. &amp;nbsp;DLLs also make it easier to separate tiers of business logic so that code can be reused across many different applications. &amp;nbsp;That said, we also recognize the benefits of writing code within the application framework itself, and are taking this into serious consideration for the future releases.&lt;/p&gt;
&lt;p&gt;AL&lt;/p&gt;
&lt;p&gt;EDN Team&lt;/p&gt;
</description></item><item><title>re: VBA and VB6 with ArcGIS: What's the Story?</title><link>http://blogs.esri.com/Dev/blogs/arcobjectsdevelopment/archive/2009/03/30/VBA-and-VB6_3A00_-The-Road-Ahead.aspx#4793</link><pubDate>Fri, 10 Apr 2009 13:28:50 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:4793</guid><dc:creator>Randy </dc:creator><description>As someone who basically dabbles, but has benefitted enormously from AML, Avenue, VBA, Python , and ModelBuilder over the years, without ever really becoming a "developer," sentences like this:

And to your second point, there are definitely advantages and disadvantages to writing code in the application tier vs in DLLs.  One thing to keep in mind however is that writing pure .NET DLLs is considerably easier than writing and deploying traditional COM DLLs.  DLLs also make it easier to separate tiers of business logic so that code can be reused across many different applications. 

Give me the heeby jeebies.

I have no idea what that means.

I just would like to know what programming language I need to learn now to keep providing useful customizations.

Currently, Python seems to work with the geoprocessing tools, but ArcObjects is what I would use for non-geoprocessing tasks (i.e., rename everything in the table of contents...or, zoom to selected features, add a bookmark, update the layout, send to printer....)

Will (does?) Python have the ability to go into that sort of area?

Thank you</description></item><item><title>re: VBA and VB6 with ArcGIS: What's the Story?</title><link>http://blogs.esri.com/Dev/blogs/arcobjectsdevelopment/archive/2009/03/30/VBA-and-VB6_3A00_-The-Road-Ahead.aspx#4968</link><pubDate>Mon, 13 Apr 2009 22:57:41 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:4968</guid><dc:creator>Hornbydd</dc:creator><description>&lt;p&gt;I've been developing ArcObjects solutions for clients and projects since ArcGIS 8.1.&lt;/p&gt;
&lt;p&gt;Usually this is in VB6/VBA and more recently I'm starting to get to grips with VB .Net. I personally &amp;nbsp;find python too slow and does not offer the rich toolkit of objects that ArcObjects has. &lt;/p&gt;
&lt;p&gt;You might as well put a gun to my head and pull the trigger if you remove the ability to write code within a MXD! &amp;nbsp;I do most of my coding within the VBA editor because its fast prototyping environment. &amp;nbsp;For example, if one of my colleagues needs a solution that the geo-processing tools are unable to achieve then I usually knock out some quick code in an MXD. &amp;nbsp;Some of my biggest and most successful projects have all run within a single MXD!&lt;/p&gt;
&lt;p&gt;As a developer I understand its considered more clever doing it in visual studio but as a consultant who has to deal with clients and colleagues with differing skill levels, resources, time and money the MXD is often the only way to deliver.&lt;/p&gt;
&lt;p&gt;Consider this...&lt;/p&gt;
&lt;p&gt;I had to work for a client to process a significant amount of data as well as providing a tool for them to use at the end of the project. &amp;nbsp;Despite them calling the shots, their own IT department would not allow DLLs... So how can I do the &amp;quot;clever&amp;quot; thing and develop an extension, the answer was an mxd!&lt;/p&gt;
&lt;p&gt;Please don't take away the ability to write custom code, forms and toolbars from a MXD.&lt;/p&gt;
</description></item><item><title>re: VBA and VB6 with ArcGIS: What's the Story?</title><link>http://blogs.esri.com/Dev/blogs/arcobjectsdevelopment/archive/2009/03/30/VBA-and-VB6_3A00_-The-Road-Ahead.aspx#5738</link><pubDate>Tue, 05 May 2009 16:05:40 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:5738</guid><dc:creator>FS</dc:creator><description>&lt;P&gt;Change is always hard to handle. &amp;nbsp;When Avenue was replaced with VB, I about had a heart attack. &amp;nbsp;But now I see how much better it is. &amp;nbsp;This will probably turn out the same. &amp;nbsp;The initial shock is hard, but then you realize how much better things are after.&lt;/P&gt;</description></item><item><title>re: VBA and VB6 with ArcGIS: What's the Story?</title><link>http://blogs.esri.com/Dev/blogs/arcobjectsdevelopment/archive/2009/03/30/VBA-and-VB6_3A00_-The-Road-Ahead.aspx#5747</link><pubDate>Wed, 06 May 2009 03:48:17 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:5747</guid><dc:creator>stevel</dc:creator><description>&lt;p&gt;When you're looking at upgrading VB Script, could you please focus on building in some error checking? &amp;quot;User Interrupt&amp;quot; doesn't help when trying to debug a complex VB Script labelling expression.&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;
</description></item><item><title>re: VBA and VB6 with ArcGIS: What's the Story?</title><link>http://blogs.esri.com/Dev/blogs/arcobjectsdevelopment/archive/2009/03/30/VBA-and-VB6_3A00_-The-Road-Ahead.aspx#5797</link><pubDate>Fri, 08 May 2009 03:14:15 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:5797</guid><dc:creator>nur</dc:creator><description>Where I can get arcgis scripting for beginner?</description></item><item><title>re: VBA and VB6 with ArcGIS: What's the Story?</title><link>http://blogs.esri.com/Dev/blogs/arcobjectsdevelopment/archive/2009/03/30/VBA-and-VB6_3A00_-The-Road-Ahead.aspx#5922</link><pubDate>Thu, 14 May 2009 21:14:33 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:5922</guid><dc:creator>alaframboise</dc:creator><description>&lt;p&gt;You may want to start with this.&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=About_getting_started_with_writing_geoprocessing_scripts"&gt;http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=About_getting_started_with_writing_geoprocessing_scripts&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;or here:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=An_overview_of_writing_geoprocessing_scripts"&gt;http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=An_overview_of_writing_geoprocessing_scripts&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Allan&lt;/p&gt;
&lt;p&gt;EDN&lt;/p&gt;
</description></item><item><title>re: VBA and VB6 with ArcGIS: What's the Story?</title><link>http://blogs.esri.com/Dev/blogs/arcobjectsdevelopment/archive/2009/03/30/VBA-and-VB6_3A00_-The-Road-Ahead.aspx#6562</link><pubDate>Wed, 24 Jun 2009 17:21:06 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:6562</guid><dc:creator>pierre.k</dc:creator><description>&lt;p&gt;What about VSTA? Does ESRI plan to support this platform in the future?&lt;/p&gt;
</description></item></channel></rss>