In MicroStation V8i, while working on a project, sheet numbering, sheet ordering, and tracking was mostly manual and hence tedious and error-prone. There were also some key limitations. Let us see what the pains in V8i were and how these have been alleviated in the CONNECT Edition.

Creating a sheet index – In V8i, the workflow for creating a sheet index was:

1. Create a link set.
2. Add sheets to the link set.
3. Adjust the sheet numbering – Note that you could not add alphanumeric numbering to sheets in V8i. Also, leading zero was not supported in the sheet numbering property.
4. Any changes in the sheets or reordering of sheets required manually updating the renumbering.
5. Total sheet count value needed to be calculated manually for inserting in the title block. Any changes to the total sheet count need to be updated manually in all the sheets, which is actually a big pain.

Sheet Numbering

Most commonly, the sheet numbering contains standards contains much more than just numeric number. For example, the US National CAD standard (v5), specifies the following components in sheet identification:

Where,

A = for alphabetical character
N = numerical character

In V8i, you could not add alphabetical character in sheet numbers. So, there wasn’t a straightforward way to achieve this. The work-around was to use Sheet Name property or Sheet Name and Sheet Number properties in combination to achieve this. However, the limitation to these workarounds was that you could not update the numbering automatically. 

communities.bentley.com/.../Sheet-numbering_2D00_V8i.mp4

Solution: In CONNECT Edition, you have the readymade Sheet Index feature. The key advantages of using sheet index over V8i manual sheet indexing are: 

1. On sheet creation itself, you can add sheets to the sheet index.
2. Sheet numbering can be alpha-numeric.
3. You can customize the sheet numbering as per your standard.
4. Total sheet count field can be used to mention the total sheet count. Changes to total sheet count are automatically updated.

communities.bentley.com/.../2677.Sheet-numbering_2D00_CONNECT.mp4

The following is a high-level comparison of the sheet numbering workflow between V8i and CONNECT. It will give you an idea how sheet numbering is efficient and fast is in CONNECT over V8i.

There are many more advantages of using the sheet indexing feature in CONNECT Edition. The upcoming blogs will cover them.

As you are aware, the Configuration dialog is frequently required to modify the location of your library files or control the behavior of certain features.

Though a very useful dialog, it certainly had a few usability issues in V8i:

• Finding a configuration variable – Since there were numerous configuration variables, it was cumbersome to find a specific configuration variable from the long list. Manually scrolling through the list was painstaking.
• Need for session restart – Some configuration variables require restarting MicroStation session after you change their values. However, there was no way to know beforehand whether the configuration variable you edit will require session restart.
• Consolidated list of defined configuration variables and their values – Say you wanted to check the location of all the DGN library related configuration variables. There was no way to get a consolidated list of all configuration variables and their values.
• Not resizable – The dialog box was fixed in size.

The following enhancements to the Configuration Variables dialog overcame many of the issues you faced in V8i and hence saves time when working with configuration variables:

• Search – You can now search for a configuration variable using the Search bar.
• Status – The Restart icon in the flags column of the configuration variables list box indicates whether the configuration variable requires session restart for the changes to take effect.
• Configuration variables list – Selecting File > Show Configuration Values opens a text file listing all the configuration variables, the Configuration level at which they are stored, and their values.
• You can resize the dialog box.

The following video demonstrates the new enhancements in CONNECT Edition.

communities.bentley.com/.../5635.Configuration-Dialog-Improvements.mp4

You like MicroStation V8i, but…

MicroStation V8i allowed elements to be “tagged” with non-graphical data referred to as Tags. Tags were stored in Tag Sets, with the tag data providing for the reporting on tagged elements.

Though a useful feature, Tags and Tag Sets had their limitations:

• Tag Sets stored locally– Tag Sets were created and stored in the active DGN file. To use a Tag Set and its related Tags in another design file, the Tag Set had to first be exported to a Tag Library, and the Tag Library subsequently imported into the desired DGN. This resulted in multiple disparate copies of the Tag Set with those copies having no relationship to each other.
• Tag Data display– Tag Data displayed in the view window as though it were text. To prevent the Tag Data from appearing in the view or when printing, the display of the Tag Data had to be disabled through a View or Print Attribute.
• Reporting– Tag reporting capabilities were limited, with Tag Report Templates first being created in an external report template file, and the resulting template ran on the tags available in the active model. This resulted in the creation of a comma delimited text file or an XML file.
• Stand-alone data – The data was effectively stand-alone in that if the data in the DGN were updated, there was no connection to any reporting that used the data.

You’ll love the MicroStation CONNECT Edition because…

The MicroStation CONNECT Edition introduces the concept of Item Types. An Item Type is a user defined set of properties that are used to describe an object or element, replacing Tag Sets. They provide many enhancements over the Tag Sets found in earlier MicroStation Versions. Some of these enhancements include:

• Stored in a DGNLib– As with many other “standards”, Item Types are typically stored in a Design Library (DGNLib). This makes them easy to distribute across your organization and share amongst Users as well as allow a CAD Manager to maintain and control the master Item Types library.
• Attach Item Data– Items may be attached to an individual element, cell, model, file, or reference.
• Possible Uses– Items can be used to label elements, in reporting, or to change the display of elements, making them vastly more functional than Tag Data.
• Reporting– When used with reporting, the report results can be placed as a MicroStation table element, exported directly to Excel, or exported as a text file with the report definition linked to the data. If the Item data is updated, the report may be rerun, and the resulting data refreshed.
• Upgrade– Tag Data and Tag Sets may easily be upgraded to Item Types.

The robust reporting features associated with Item Types and Items can be used to generate door and window schedules, a bill of materials, or perform simple quantities. Items attached to elements can be used to repurpose geometry, changing the display of elements not just at print time, but rather while a User is working in the design.

Item Types and Items are a powerful addition that can be found in the MicroStation CONNECT Edition!

You like MicroStation V8i but...

In V8i you can create parametric, feature-based solids, using Feature Modeling tools. Parameters used to create features like chamfer, fillet, hole, etc., are stored in the design and can be edited using the Modify Parametric Solid or Feature tool. You can edit such solids by changing the parameters used to create them or by selecting them and using the handles to make changes interactively. You can manage the features using the Feature Manger tool.

However, feature modeling has certain limitations:

• You must work with multiple tool settings to create, edit and manage feature solids like the Feature Solids tool, Modify Parametric Solid or Feature, Feature Manager, Parameter sets, etc.
• Constraints cannot be applied to 3D elements.
  
• Constraint markers are not very intuitive.
  
• Assigning variables, equations and expressions is complicated and time consuming due to lack of a consolidated tool to create and manage variables and variations of a feature solid.
  communities.bentley.com/.../3731.Video-1.mp4
• Input elements used to create solids, cannot be accessed directly on solids for modification. You must access the contextual menu on specific handles to modify the element’s properties.
• Feature Manager dialog– a separate Feature Manager dialog is used to view and manage features. Element Information dialog does not display any feature or constraint information.
• Feature Cell - parametric geometries are placed as feature cells. Feature cells cannot be placed as shared cells. Any variations to the cells can be applied only through the Edit Feature Cell dialog and cannot be managed in the Element Information dialog.
  
  

You'll Love MicroStation CONNECT Edition because...

MicroStation CONNECT Edition provides advanced parametric modeling features which greatly simplify the workflow of creation, modification, placement and animation of complex parametric geometries.

• Solids Ribbon tab - All solid features creation and modification tools have been consolidated in the Solids ribbon tab for convenient access.
• Variables dialog - allows creation and management of variables and variations at a single location. Equations can be easily defined in the Expression builder dialog accessible from within the Variables dialog.
• Constraint support has been extended to 3D elements, (Solids and Surfaces).
• Profile sketches or input elements can be accessed and modified directly on elements.
• Properties dialog can handle all functions that are taken care of by the Feature Manager and Edit Feature Cell dialog, like editing values of parametric elements and sketches, reordering feature priority, deleting or disabling features, etc.
• The user-friendly interface represents geometric and dimensional constraint markers and profile information like Degree of Freedom count, clearly and conveniently on the parametric elements.
  
• Parametric Cells - parametric components can be created on models that can be placed as parametric cells. Once placed, different variations of the same cell can be applied from the Properties dialog or the Variables dialog.
  Below video shows different variations of a bolt for different sizes, with and without the bottom hole feature.
  communities.bentley.com/.../5314.Video-2.mp4
• Light weight instances - Instances of complex parametric cells are efficient and light weight when placed and can be easily managed from the Variables dialog.
• Interactive Assemblies - It is possible to create interactive assemblies of parametric elements with other elements, where distance between them can be given a dimension constraint. Elements thus constrained, adjust to variations of the parametric elements.
  communities.bentley.com/.../2260.Video-3.mp4
• Animation– Applied 3D constraints are respected while animating the constrained geometries.
  
• Parametric cells behave as Shared cells when placed, which means the cell definition is stored in the DGN file and subsequent placement of these cells does not need the cell library to be attached again.
  communities.bentley.com/.../5807.Video-4.mp4

In storm and sewer systems with hilly terrain, depth of cover may vary significantly over the length of a pipe. Did you know that the CONNECT Edition of Bentley's OpenFlows storm and sewer products can use Terrain Models to capture more accurate change in cover along pipes, and consider it during Automated Design? This helps ensure that your cover constraints are met not just at the pipe ends, but along the entire pipe length. Watch the below short demonstration to see how.

Applicable Products: SewerGEMS, SewerCAD, StormCAD, CivilStorm: CONNECT Edition

To learn more, check out the additional resources in the "See Also" section below.

https://youtu.be/pL0-wWNIQzg

Want to see more? Sign in, click the More button and turn blog notifications on. Or, subscribe to our YouTube Channel.

This video is part of a growing library of useful information designed to provide effective tips and information about time-saving product features within Bentley’s OpenFlows products. Be sure to check back frequently to view the latest video. Better yet, subscribe to this blog by turning Notifications On.

Douglas Miranda
Bentley Systems, Inc.

See Also

Using Downstream Trace and Digital Terrain Models

For many years we have written dialog item hook functions using procedural code.  You can continue that way with MicroStation CONNECT, but the MicroStationAPI offers a better way: dialog and dialog item hook classes.

The hook classes replace the MDL switch decision tree with the DialogHookHandler and DialogItemHookHandler classes that provides virtual event handler methods such as _OnCreate().  The ListModelManager class goes one step further: it provides dialog item specific methods to assign and deallocate the ListModel using by ComboBox and ListBox dialog items.

ListModelManager is a template class.  It offers specialised handlers for ComboBox and ListBox dialog items.  They improve your code by using the correct set/get methods and by always destroying the ListModel in the _OnDestroy() event.

Discover how MAXSURF and photogrammetry are being used to preserve our maritime history ...
https://www.linkedin.com/pulse/using-photogrammetry-preserve-our-maritime-history-dougal-harris/?published=t&fbclid=IwAR0isCWnIisXGonhze7crgnzJ3E1IWMoGiJLHVVypADedT_J2m-caxkO0xM

You like MicroStation V8i, but…   

MicroStation V8i has been in use since it was first released in November of 2008, effectively serving the Bentley user community for many years. It has evolved to become a proven and stable platform, considered by many to be an indispensable part of their design and engineering workflows. However, this technology is over 10 years old and is no longer being updated. And while V8i has met the needs of organizations, and had done so well, the MicroStation CONNECT Edition offers many new enhancements that can speed production and improve workflows. With future development in MicroStation V8i having ceased, you may wonder what to do.

You’ll love the MicroStation CONNECT Edition because…

It is the solid foundation of V8i that the MicroStation CONNECT Edition is built upon. The CONNECT Edition offers many exciting benefits and productivity enhancements that Users will find to be compelling reasons to upgrade their software. Some of these enhancements include:

• Data interoperability– Enabling MicroStation to better work with other file types including DWG, IFC, and SketchUp just to name a few.
• Item Types– User defined sets of properties used to describe an object or element.
• Reports– Used to extract and present data from a DGN file.
• Tables– A new MicroStation element type, similar in operation to that of an Excel workbook, used to present data in a tabular format.
• Sheet Index– A centralized and structured collection of sheets used for displaying all sheets in a project (WorkSet) that is useful in creating a construction document set.
• Parametric Modeling– Parametric modeling uses parameters to control the dimensions and shape of elements, which may be modified later, with the model updating to reflect the modification.
• Labels– A cell used for labelling that can maintain an association to the element being labelled, with the label driven by various types of properties or Item data.

The MicroStation CONNECT Edition can coexist alongside MicroStation V8i, with both versions being installed on the same workstation. This “parallel installation” allows a User to work on a project using the required version of MicroStation as directed by project or client needs. Existing projects that are far enough along can be completed in V8i (when it makes sense to do so), while new projects can be undertaken using the MicroStation CONNECT Edition.

Some of the benefits of a dual installation include:

• Workflow continuity– When an existing project is far enough along that it makes sense to complete that project in V8i, project team members can do so allowing project development to continue uninterrupted, with new projects beginning in the MicroStation CONNECT Edition as desired.
• Separate installation folders– The MicroStation CONNECT Edition and MicroStation V8i each utilize their own installation folder, allowing the applications to be isolated from each other.
• Separate User Preferences– Each MicroStation version uses a separate set of User Preferences that are unique to the specific version.
• Design files– The DGN file format remains essentially the same in the MicroStation CONNECT Edition. This allows a file to be opened in either version of MicroStation.
• CAD standards files– Most CAD standards files (i.e. cell libraries, DGNLib’s, RSC files, etc.) do not change and will work “as is” in the MicroStation CONNECT Edition without requiring additional development or the need to upgrade the file format. There are notable exceptions to this such as MDL applications and VBA’s.

The installation of both MicroStation V8i and the MicroStation CONNECT Edition on the same workstation helps ease the adoption of a new software version. This effectively lowers the learning curve by allowing users to become familiar with the MicroStation CONNECT Edition’s interface and updates while continuing to remain productive in existing V8i based projects.

Load the MicroStation CONNECT Edition and begin your CONNECT Edition implementation by initiating a pilot project today!

I recently download MicroStation CE SDK, and running into a series of issues when trying to build SDK examples. Thought it's a good idea to share the solutions I found...

My environment: Win 10 + Visual Studio 2017 Community + MicroStation CE (v10.11.00.36) + MicroStation CE SDK (v10.11.00.42)

Issue 1: when building SDK examples, got error 'VS2015_DotNetToolsDir was not defined'

Solution: install '.NET Framework 4.6.1 Developer Pack and Language Packs' AND update 'C:\Program Files\Bentley\MicroStationCONNECTSDK\mki\VCVarsQueryRegistry14.mki as follows

change line 97 & 104

from: HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Microsoft SDKs/NETFXSDK/4.6
to: HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/Microsoft/Microsoft SDKs/NETFXSDK/4.6.1

Issue 2: when building SDK examples, got error 'VS2015_FrameworkVersion64 was not defined'

solution: change visual studio 2017 installation by clicking on 'Desktop development with C++' first then ticking ON 'vc++ 2015.3 v14.0 toolset for desktop' (see the pic below) AND update 'C:\Program Files\Bentley\MicroStationCONNECTSDK\mki\VCVarsQueryRegistry14.mki as follows

change line 133 & 140

from: HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/VisualStudio/SxS/VC7
to: HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/Microsoft/VisualStudio/SxS/VC7

Issue 3: mt.exe is not a regonized cmd

solution: install Win 10 SDK AND add 'C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\' (where mt.exe resides) in the env var path

HTH

Think about upgrading from Navigator V8i to Navigator CE? You need to be aware of all these changes...

Major Changes in Navigator CE as compared to Navigator V8i:

• can only open mobile i-models (.imodel)
• can NOT open files directly from ProjectWise
• can NOT attach ref files
• can NOT create overlay files

Meaning we can NOT use the same way to work in Navigator CE as V8i!

• first off, we need to convert regular i-model (.i.dgn) to mobile i-model (.imodel). You can use 'dgnV8converter.exe' delivered with MicroStation CE update 11 for the conversion 
• you can open mobile i-models either from local PC or Project Share Service in ProjectWise Project (formerly known as Connected Project)
• because we can NOT attach ref files interactively in Navigator CE, package mobile i-models (contains all refs you need) have to be built in advance (I know it's crazy, right before design review, you find a ref is missing, now you need to rebuild the whole package i-model instead of just building the ref then attach it!)
• because NO overlay files any more, all the markups\comments can only be captured in Issue Resolution Service in ProjectWise Project

Overall, ProjectWise Project becomes a prerequisite to run Navigator CE. If you are not familiar with it, better to catch up!

communities.bentley.com/.../4540.HybridBlog.mp4

Are you a Project Manager, Team Leader or Early Adopter who wants to stay on the cutting edge of Bentley technology? Do you want to use and adopt many of the new features and workflows but just cannot due to your projects being at V8i?

Then we have some great news for you! The MicroStation CONNECT Edition makes it easy for you to collaborate on your data with both versions of MicroStation simultaneously. You can easily migrate a V8i based project to the MicroStation CONNECT Edition without cloning or copying the data and resource files.

In short, we can point the MicroStation CONNECT Edition to the location of the data files, simple as that. While going from a V8i project to a MicroStation CONNECT WorkSet is certainly the preferred path, Bentley understands that in some cases you may not be able to “flip a switch” on a Project moving it forward to a CONNECT Edition WorkSet.

Consider this, there is an existing Project functioning just fine in MicroStation V8i. You need to be able to create and edit geometry in MicroStation V8i, but would also like to take advantage of the modern features such as Reporting from DGN elements and Placing a Table from a Report or gain improved productivity through Sheet Management or create custom element properties with Item Types.

Next, you will review the steps needed to direct the MicroStation CONNECT Edition to the location of an existing V8i Project. The MicroStation CONNECT Edition will create the folders and files needed for it to become a MicroStation CONNECT Edition WorkSet, including the .dgnws and the .cfg, placing them in the same location that MicroStation V8i stores its project data. These steps will allow you to continue working on a V8i based Project while taking advantage of the many new features and enhancements found in the MicroStation CONNECT Edition.

You are welcome to read the steps and try them on your own. Attached is the same dataset, along with a video, showing the entire process.

1. Locate and note the exact path of the V8i based Projects folder. For this example, it is found using a UNC path (\\NA2257\_ProjectData\Projects). Ensure that you have Read/Write access to the folder location.
2. Create a MicroStation CONNECT Edition WorkSpace, called “Projects”. The MicroStation CONNECT Edition will create a CFG file in the CONNECT based \WorkSpaces folder. This configuration file will simply point to the V8i based Projects folder (\\NA2257\_ProjectData\Projects). The process will also create two folders under the shared \Projects folder, one for WorkSets and the other Standards. Keep in mind the name of the WorkSpace in the CONNECT edition MUST be named the same as the existing folder in which the V8i Workspace data is stored. In this case, this was Projects.
3. Navigate to the location of your “Hybrid” project, in this case, \\NA2257\_ProjectData\Projects. You will note the existence of HybridProject.pcf and the Project folder structure for the V8i Project.
   1. Copy and rename the Project Configuration File, HybridProject.pcf to HybridProject.cfg.
   2. Move the new HybridProject.cfg to the shared location:  \\NA2257\_ProjectData\Projects\WorkSets
4. Using your favorite text editor, edit HybridProject.cfg. This file is a copy of the HybridProject.pcf from MicroStation V8i and needs to be modified if it is to be used in the MicroStation CONNECT Edition. The following changes need to be made:
   1. Replace any instance of the variable $(_USTN_PROJECTDATA) with $(_USTN_WORKSETROOT).
   2. Remove the variable _USTN_PROJECTDESCR =
   3. Remove the variable MS_SETTINGSDIR < $(_USTN_PROJECTDATA)data/
   4. Remove the variable MS_SETTINGSOUTDIR = $(_USTN_PROJECTDATA)data/
   5. Change the title from Project Configuration to WorkSet Configuration.
5. *** The most critical step is to define the USTN_WORKSETROOT variable. This variable and _USTN_WORKSETNAME are new to the MicroStation CONNECT Edition. Define the variable as:

_USTN_WORKSETROOT = //NA2257/_ProjectData/Projects/$(_USTN_WORKSETNAME)/

This variable will set where the WorkSet is located. It also ensures that certain variables are set at the proper level in the MicroStation CONNECT Edition. Don’t forget to Save the cfg after editing.

Now you might ask, what about all the other things set at other levels in the WorkSpace in MicroStation V8i. Yes, those need to be addressed. This method is best suited for simple Workspaces and Projects that set symbology related functions. However, it is possible to create your WorkSpace for the CONNECT Edition either manually or via Configuration Migration/Configuration Assistant.

Note: Look for a separate blog on using Configuration Migration.

At this point, you can open the MicroStation CONNECT Edition, with the WorkSpace Projects and the WorkSet HybridProject.

Open the file LandscapeRD_1.dgn. You will note that in the \_ProjectData\Projects\WorkSets folder where the HybridProject.cfg exists, there will be another file that was created, the HybridProject.dgnws. This file is used to store WorkSet properties, the Sheet Index, and WorkSet related links.

Once you have the dgn opened in the MicroStation CONNECT Edition, let's test out the idea of a “Hybrid” WorkSet. From Reports, using Place as a Table, add the table to the model Ground Cover Summary Report as displayed.

Then, using MicroStation V8i and the HybridProject, note the newly placed table. The table placed from the MicroStation CONNECT Editon can also be seen in MicroStation V8i. If the table needs to be edited or updated, this needs to be done in the MicroStation CONNECT Edition.

The concept of creating a Hybrid project is really a temporary situation. Ideally, you will move the project to a CONNECT based WorkSet. But this concept gives you an alternative for simpler projects that need to be worked on in both versions. When the team members are ready you can then archive the V8i project and switch everyone over to the MicroStation CONNECT Edition.

Take advantage of the great things the MicroStation CONNECT Edition offers sooner rather than later. Try out a Hybrid WorkSet now!

“The secret of getting ahead is getting started. The secret of getting started is breaking your complex, overwhelming tasks into small manageable tasks, then starting on the first one.”
~ Mark Twain (1835 - 1910)

This great quote can be applicable to anything.  Even when it comes to MicroStation.  Let’s say that you are a CAD manager.  You have the responsibility to provide a trouble-free working environment that adheres to your company’s design practices and standards.  Now you are tasked with upgrading to the latest version of MicroStation, the MicroStation CONNECT Edition.  As with anything in life, careful planning and due diligence are going to dramatically increase your success in achieving your goals and endeavors.

Now with regards to the MicroStation CONNECT Edition, there are many items to consider and decisions to be made when planning a successful migration.  It is important to put in place a successful migration plan that includes discovery, planning, configuration, development, training, user acceptance, deployment, coaching, and best practices.

Completing a Pilot Project should be considered prior to full deployment.  Pilot Projects provide robust testing of the new configurations on real-world projects, allowing for easy adjustments to configurations and workflows prior to full production.

When all the testing, configuration, training and a Pilot Project have been vetted, you arrive at the point where V8i projects will be migrated.  One migration path is to move directly from your current MicroStation version to MicroStation CONNECT Edition.  However, flipping a switch may be easier said than done.

In some cases, the recommendation is to maintain some V8i projects on the current version and migrate the other V8i projects forward over time.  The reason that this incremental approach will be successful is that for one, there is not a file format change.  There is no need to upgrade a DGN file to be opened in the MicroStation CONNECT Edition.  This, of course, goes without saying for other types of resources that a DGN file relies upon.  For example, design and cell libraries, which are essentially DGN files with a different file extension.  Simply put, all the file types that were used in V8i projects will work just same in the MicroStation CONNECT Edition.

Furthermore, with this workflow of an incremental approach, it is assumed that any new projects started after MicroStation CONNECT Edition has been green-lighted for production, would be utilizing the MicroStation CONNECT Edition.  Those new projects started with the MicroStation CONNECT Edition would not encumber any issues referencing dgn files from V8i projects that have yet to be migrated.

With Update 11 for the MicroStation CONNECT Edition, came the Configuration Assistant (Technology Preview).  This automated tool is meant to help a CAD Manager to quickly create MicroStation CONNECT Configurations from V8i workspaces.  It can be accessed from the WorkSpace menu on the Work Page.

So, that all being said, MicroStation CONNECT Edition presents no big filter or great hurdle that requires the conversion of these file types.  V8i generated DGN files are no different that MicroStation CONNECT Edition generated DGN files.  Hence, there is not a great need or rush to migrate all projects in the V8i workspace in one go.

Starting with the MicroStation CONNECT Edition, Bentley has been releasing quarterly updates as a method of continuous improvement.

The Configuration Migration Wizard was added to Update 4 of the MicroStation CONNECT Edition. It helped migrate legacy V8i Workspaces to the MicroStation CONNECT Edition’s Configuration.

Configuration Migration accomplished three main tasks.

• It identified any MicroStation V8i based products on the machine and listed the location of the default Workspaces.
• In those workspaces or in a location of your choosing, it converted any User, specifically the .ucf to a WorkSpace based .cfg.
• It converted any Project, specifically the .pcf to a WorkSet based cfg.

The Configuration Migration Wizard did not change the location of your V8i data such as .dgn files and the Workspace configuration files. It simply created .cfg files that pointed to them, in effect, the MicroStation CONNECT Edition pointed to the MicroStation V8i location.

In an effort of continuous improvement, beginning with Update 12 of the MicroStation CONNECT Edition, we introduce you to the new Configuration Assistant.

This tool will quickly become your best friend, a sort of automated MicroStation CONNECT magician in a box. The Configuration Assistant is designed to help you create a CONNECT based Configuration from an existing V8i based Workspace.

The new Configuration Assistant accomplishes a few more tasks than Configuration Migration.

• Identifies installed MicroStation and MicroStation based products on your machine and lists the default WorkSpaces for each product.
• Converts legacy User (.ucf) to WorkSpace (.cfg).
• Converts legacy Project (.pcf) to WorkSet (.cfg).
• Moves Site level configuration (by default set to ..\\WorkSpace\Standards) to Organization level (..\\Configuration\Organization\).
• Optionally copies all the project data files.

Configuration Assistant is a fantastic tool, but it is a bit different than the previous Configuration Migration Wizard.

Configuration Assistant will still identify any MicroStation V8i based products on your machine and lists the location of the default Workspaces.

Configuration Assistant lets you define where the destination of the new MicroStation CONNECT based WorkSpace and its associated WorkSets are to be located. It will configure the MicroStation CONNECT Edition to look for its configuration at this new location, in addition to what it is currently using.

Configuration Migration will migrate a set of Workspace configuration files, with this being a combination of a V8i “User” and “Project”. These are migrated to a MicroStation CONNECT Edition WorkSpace and WorkSet. It does not automatically convert all Projects (.pcf files) within the workspace, you can choose. The first time this is run, it will convert the selected Users (.ucf) and matching groups of Project (.pcf). Each subsequent time it is run on that the User the user configuration file will already have been converted, and just the additional Project will be processed with the resulting WorkSet being placed into the existing WorkSpace.

Running Configuration Migration is simple. After selecting the V8i-based product from the drop down, the Configuration Assistant will read a valid MicroStation V8i-based workspace configuration.

Again, a combination of a .ucf and a .pcf, the Configuration Assistant will display both Workspace and Project.

One other differentiator is that Configuration Assistant will not only migrate the V8i Workspaces (Users) but you can choose to also migrate any data files as well. So rather than just taking a .ucf and creating a .cfg, it can also clone or copy the data to your desired location.

You can also selectively pick MicroStation V8i Users or migrate all of the Users. It also lets you do the same for Projects, but keep in mind WorkSets (MicroStation CONNECT equivalent of a Project) are tied to ONE particular WorkSpace.

From there you define where the destination of the new WorkSpace is to be located. This can be inside the MicroStation CONNECT Edition, or any custom location of your choosing. And the best part, there is no extra configuration needed. MicroStation will edit the correct variable to locate your new WorkSpace and WorkSet location.

Once the location is chosen, an informational dialog appears informing you if the migration was successful, listing each and every User and Project that was migrated to the MicroStation CONNECT Edition’s WorkSpace and WorkSet.

Give Configuration Assistant a try today, not only a great new tool to assist in migrating your User and Projects to WorkSpace and WorkSets but also a great example of continuous improvement of the MicroStation CONNECT Edition.

I just finished teaching a couple of InRoads v8i SELECTseries 2 training classes.  I hope they’re my last.

There are a hundred reasons to upgrade to OpenRoads as quickly as you can.  My personally favorite reason is that OpenRoads is just more fun to work with.  I’d argue that that’s probably the most important reason, but I save that argument for another post.

As a trainer and developer of training, there are lots of reasons why teaching OpenRoads is more enjoyable that teaching the old stuff.  The most pervasive reason:  One Format!

Ignoring all the amazing NEW things you can do with OpenRoads that your old software, even if you’re doing the exact same work, OpenRoads is dramatically easier to teach because it’s dramatically easier to learn.

Why?  One Format!

Being fully committed to Bentley’s universally sharable data platform – the dgn – truly revolutionizes how you teach, how you learn, how you use Bentley’s Civil Software.  It’s easier, it’s cleaner, it’s WYSIWYG.  What You See Is What You Get eliminates whole categories of inefficiency and confusion.  It’s reason alone to move forward, but, of course, there are many reasons.

I’d start my old InRoads classes explaining the similarities and differences between the three primary data formats:  graphics, geometry and surface. Why three?  Because all three were incomplete solutions due to software limitations.

I’d explain that my favorite tool in InRoads was Select All and Delete – because I couldn’t trust the graphics.  Think about that.

I’d explain why we needed a Geometry file format.  I’d explain that because we couldn’t trust the graphics, we had a DTM file format where we’d build our “real” data model.

Neither DTM nor ALG format was even visible.  That which was visible could not be trusted.

Heck of a foundation…

It had been several years since I taught old InRoads, I knew I’d have to suppress my impatience.  To someone who has worked in the One Format Truth, the old system seems as efficient as using punchcards.

But I had also forgotten (willfully?) a whole slew of other inefficiencies and burdens on the designer because of the splits.

OpenRoads: One set of tools.

But in InRoads:  three formats meant three separate (mostly) parallel palettes of tools to perform the same tasks.  This doesn’t triple the training time, maybe only doubling it. 

OpenRoads has one set of tools because it only has one format.  OpenRoads uses MicroStation tools whenever it can, like the Trim tools and Snaps. 

Consider a fillet in InRoads.  MicroStation has a Trim tool, InRoads has a Surface Feature Trim tool, and InRoads Geometry has techniques to trim a tangent.  MicroStation had a Fillet tool.  InRoads Geometry had Curveset tools and InRoads Surfaces had a Fillet tool.  The Surface Fillet Feature tool is a labyrinth that confuses even the experts.

On an individual or corporate level: which is easier?  One comprehensive and complete way to do things or three incomplete overlapping partial solutions that you need to merge to a solution?  Easier to learn, easier to troubleshoot, easier to manage, to archive, to resurrect? 

I loved InRoads, I thought I was happy.  Ignorance may be bliss, but it shouldn’t be a strategy. 

It’s time.  Come into the light.  Open up to OpenRoads.

Following our users' requests we decided to add the beloved Set Element Elevation tool, previously part of the old CivTools MDL application, to MicroStation CONNECT Edition update 12.

You can find this tool in the Manipulate group of the Home tab in the Drawing workflow.

This tool lets you set the Z elevation of all vertices of all selected elements by entering either an absolute or incremental Z value. It is very easy and simple to use: just enter the new Z, chose Absolute or Delta and select the elements/accept! 

The tool is also documented in MicroStation's help in case you were not familiar with the old CivTools.

Do you want to know more about MicroStation CONNECT Edition Update 12? Check out this video or look at MicroStation's help for more details!

In MicroStation CONNECT Edition Update 12 you can now generate reports only on item types in a selection.

The option is available in the report definition properties, where you can choose between "All elements", "Current" or "by Fence" selection types. All very simple and easy to setup and use!  

Do you want to know more about MicroStation CONNECT Edition Update 12? Check out this video or look at MicroStation's help for more details!

Ankündigung vom 12. März 2019

Das MicroStation SDK Team freut sich Ihnen mitteilen zu können, dass das MicroStation CONNECT Edition SDK Update 12 (U12)  ab sofort verfügbar ist. Dieses aktuelle Release liefert eine Anzahl von Erweiterungen in den folgenden Bereichen:

1. Zusammenfassung
   • Microsoft Visual Studio 2017 Professional (oder besser) ist die Standard-Toolset-Anforderung
   • Rekompilieren Sie MDL-Anwendungen aufgrund neuer Standard-Toolset-Anforderungen
   • Laufende Updates: APIs, Dokumentation, Beispiele
     
2. Dokumentation
   
   
   • Letzte Änderungen(..\MicroStationCONNECTSDK\Documentation\Index.html)
     • Themen
       • Installation > Installation Requirements
       • What's New > "What's new in the SDK"
       • [ChooseSDKUpdateVersion]
       • MicroStation CONNECT Update [ChooseSDKUpdateVersion] Deprecated functions
         
         
     • Hinzugefügt
       • Documentation\chm
     • Blog: Bentley Communities - MicroStation Programming Blog

3. Developer Shell
   
   
   • Unterstützt wird jetzt auch Microsoft Visual Studio 2017
   • bietet Support für:
     • Visual Studio (vorgabemäßig oder benutzerdefiniert) Entwicklungsumgebung (_SDKINITVS, _SDKVSTOOLDIR, _SDKVSTOOLCMD)
     • SDKMacros Initialisierung (_SDKINITMACROS)
     • Tool/script laufende Updates
       

4. Includes und APIs
   
   
   • Hinzugefügt
     • DgnPlatform\PickList.h
       • PickList and PickListValue
     • Geändert
       • DgnPlatform\DgnPlatform.h
         • DrawPurpose::VueRender
       • DgnPlatform\ECReportNode.h
         • GetSelectionScopeOption / SetSelectionScopeOption
       • DgnPlatform\LxoSetup.h
         • RenderOutputArray
       • DgnPlatform\SolidKernel.h
         • ISubEntity
       • Geom\BSIQuadrature.h
         • GetXYEval - @param [out] w weight for sums
       • Geom\ClipPlaneSet.h
         • ClipPlanarRegion / ClipAndMaskPlanarRegion
       • Geom\CurvePrimitive.h
         • Neues Thema: ICurvePrimitive > Fraktionierte Position entlang einer Primitiven
         • CreateAustralianRailCorpBearingRadiusLengthRadius
       • Geom\DPoint3dOps.h
         • FixupAndTriangulateSpaceLoops - @param [out] xyzOut zurückgegebene Koordinaten
       • Geom\DSpiral2dBase.h
         • Stroke - @param [in] spiral Spirale für Stroke
         • StrokeToAnnouncer
         • @param [out] minInterval kleinste erlaubte Nummer für Intervall
         • @param [out] maxStrokeLength maximal erlaubte Stroke Länge
       • Geom\transform.h
         • MultiplyX / MultiplyY / MultiplyZ
       • mki\AssertToolSet.mki
         • Adjust capabilities: BUILD_USING_VS2017 and BUILD_USING_VS2015
       • mki\DefaultToolSet.mki
         • Anpassen des Default Toolsets: BUILD_USING_VS2017
       • mki\winntmdl.mki
         • Anpassen von CCompOpts + -fp:precise
           

5. Beispiele
   
   
   • DgnEC\DgnECNativeCrudExample
   • DgnEC\PickListExamples
     • ManagedExample
     • NativeExample

6. Libraries
   
   
   • Keine
     
7. Voraussetzungen
   
   
   • Microsoft Visual Studio 2017 Professional (oder besser) ist die Standard-Toolset-Anforderung
     • Workload Abhängigkeiten
     • .NET Desktop Entwicklung
     • Desktop Entwicklung mit C++ (liefert: DIA SDK)
     • Universelle Windows Plattform Entwicklung (liefert: Windows 10 SDK, oder Download)
       
   • Installation und Konfiguration
     
     
     • Installation: Get set up, oder
     • Konfiguration: Workloads und Komponenten, oder
     • Änderung: Benutze Commandline Parameter und Workload und Komponentenids
       
   • Änderungen Ablage für Toolset
     
     
     • Compiler Tools Layout in Visual Studio 2017
     • How to: Setzen von Umgebungsvariablen für Visual Studio Commandline (VSDevCmd.bat)
       
     • Hinweis: Microsoft empfiehlt das Binden von 1 Toolset (Version) pro 1 Entwicklungsshell (Umgebungsinstanz).
       
   • MicroStation CONNECT Edition SDK nativ (C/C++) und managed Code (.NET Addins) Entwicklung benötigt:
     • Microsoft Visual Studio 2017 Professional (mit aktuellen Patches)
     • Microsoft .NET Framework 4.6.2 Runtime (benötigt für Windows 2012 und früher)
       

8. Bekannte Probleme, Lösungen, Besondere Änderungen
   
   
   • Rekompilieren Sie MDL-Anwendungen aufgrund neuer Standard-Toolset-Anforderungen
     
9. Release Bemerkungen
   
   
   • Mit Installation der MicroStation CONNECT Edition SDK wird empfohlen Ihren Desktop und/oder Startmenü Shortcut zu ändern und die Eigenschafte "Starten alsAdministrator" zu aktivieren.. Dies hilft sicherzustellen, dass Dateien und Ordner erfogreich erstellt werden können und benötigte Erlaubnisse für von Windows geschützten Ordnern zu erteilen.
   • MicroStation SDK Versionen sind normalerweise innerhalb von 2 Wochen nach der Freigabe einer betreffenden MicroStation Produkt Version zum Download verfügbar.
   • Um maximale Kompatibilität und Stabilität  Ihrer Applikation sicherzustellen:
     • Stellen Sie sicher, die aktuellste MicroStation CONNECT Edition SDK und eine möglichst genau passende MicroStation Produktversion zu benutzen
     • Es wird dringend empfohlen bereits vorhandene Applikationen für jede neue MicroStation Produkt und SDK Version neu zu kompilieren
       

10. Ressourcen
    
    
    • MicroStation CONNECT
      • MicroStation CONNECT Edition SDK Downloads
      • MicroStation CONNECT Edition (Produkt) Releases
      • Neu in MicroStation CONNECT? (für neue / erfahrene Entwickler)
    • Bentley CONNECTION Center Bentley Online Serviceportal
    • Developers and Programming - Forums Suchen und posten von Fragen zur Bentley Programmierung
    • Bentley Developer Network Program - Forum Suchen und posten von BDN Programmfragen
    • https://www.bentley.com/en/software-developers lErfahren Sie mehr über das BDN Programm
    • Bentley Developer Network Inquiry/Contact Us Form - SDK Zugriff und Download von SDK Ausgaben
    • Support Lifecycle Policy, Privacy, Terms of Use, EULA (Rechtliche Hinweise und Datenschutz)
      
      
      

Link zur englischen Ankündigung

This is a reminder of our upcoming regularly scheduled patch and maintenance weekend - March 15 thru 17th for Bentley ProjectWise Managed Services. We apologize for any disruption in service you may possibly see but the maintenance of your servers is pertinent for system health and security.

Microsoft releases its security patches on the second Tuesday of each month. Bentley Managed Services patches all hosted servers on the following weekend during non-business hours per the location of the hosted servers. Please view the Microsoft Security Updates site for the release notes for this month's patching. 

During each patch weekend, Bentley strives to keep the planned outage to 30 minutes or less per server farm (FQDN).

To see a schedule of all 2019 patch weekends, please see the Bentley patch calendar  located within the Bentley Communities ProjectWise Hosting Services web site.