I found several errors before getting an output working from the code download.

1. Property ':Groups' not found

• Updated AlignmentReport.cs groups and users to :Groups and :Users

2. Property 'approximate_messages_count' not found

• Fixed messages_count to approximate_messages_count in Groups.cs

3. Line 10 YAML - The string was not recognized as a valid DateTime

• Never rather than date statement that could be fixed by the same coding as your lastaccessed.
• I just copied another date to quickly get past this.

4. Expected 'StreamEnd', got 'DocumentStart'

• YAML file - removed the --- from between groups and user sections

5. Property 'community_message_count' not found

• Fixed public_message_count to community_message_count in User.CS

I should mention I'm in Australia so not sure if some field names differ based on geolocation.
And this is where I encounter the issue you already have regarding group admin outputs.

Native mode converts legacy external groups to regular connected communities. Those support external users (AAD B2B), but there is currently a gap with how to quickly get users up and running because they lose access when native mode alignment happens. Think of ways we can provide something to help admins move forward and implement support for it.

unicode chars do not survive the transformation

a group with this name in the .yml file
Nødkommunikasjon i jernbanetunnel

becomes this in the processed file
Nødkommunikasjon i jernbanetunnel

The current app has hardcoded defaults for the output separator (comma) and the extension of the output files (.CSV). As a result, embedded commas in data causes problems with opening the results. By adding an options dialog, these things can be configurable.

Support is needed for tabs. Adding a \t as a separator should enable tab separated output.

The csv files that are generated by this tool are not compliant with RFC 4180, specifically the part of the RFC that stipulates that:

Each line should contain the same number of fields.
Fields that contain a special character (comma, CR, LF, or double quote), must be "escaped" by enclosing them in double quotes (Hex 22)> .

Since none of the field values are encapsulated in double quotes in the CSV that is created by the NMARC tool, it means that "," characters in field values will be parsed as a delimiter, and not as an "escaped" coma...which causes problems for field values like "this is, a field value, with many comma's". The comma's in a field value like that should not be parsed as a delimiter, but as an "escaped coma".

As we have a number of groups which contain a comma in their name, the generated CSV file fails to import correctly to excel

would it be possible to change the delimiter to another value - or even better enclose the values in "" so excel can import/break columns correctly
would work
"3479542","Name of,Department","internal","unlisted","active","7","2/2/2018 2:09:15"

splits one value into two columns and messes up format in excel
3479542,Name of,Department,internal,unlisted,active,7,2/2/2018 2:09:15

Output files are not obviously CSV files and these should be changed from .TXT because they don't open in Excel by default.

Follow the guide at https://learn.microsoft.com/en-us/dotnet/core/porting/upgrade-assistant-winforms-framework and ensure that HiDPI still works.

The other_community_guests properties contains users that don't fit into the active category of guests which are already supported.

Currently, the tool runs and displays a random assortment of information. It would be good to show total numbers of objects and list all of the output files containing that data.

When parsing the YAML some items like groups, the parsing is quite complicated. Compare the group_admins element for these groups:

groups:
  123456:
    name: Test Group
    id: 123456
    type: internal
    privacy_setting: private
    state: active
    messages_count: 321
    last_message_at: 2020-04-30 22:35:25.506949969 +00:00
    o365_connected: true
    group_admins:
      with_o365_creation_rights: []
      without_o365_creation_rights:
      - [email protected]
      - [email protected]
    member_counts:
      internal: 91
      external: 0
    uploaded_file_counts:
      yammer_files: 32
      sharepoint_files: 0
  456789:
    name: Test Group 2
    id: 456789
    type: internal
    privacy_setting: private
    state: active
    messages_count: 321
    last_message_at: 2020-04-30 22:35:25.506949969 +00:00
    o365_connected: true
    group_admins: All Yammer Verified admins
    member_counts:
      internal: 91
      external: 0
    uploaded_file_counts:
      yammer_files: 32
      sharepoint_files: 0

Sometimes group_admins is a simple string which gets parsed easily with the declarations, but at other times this element is a complex structure. Fixing this requires the creation of an IYamlTypeConverter for each of these complicated sections of YAML.

My first attempt was successful for the last_date_accessed element (see LastAccessed and LastAccessedTypeConverter classes.) When I implemented this for the group_admins element there were some issues with the internals of YamlDotNet getting out of sync when deserializing. It would overrun into the member_counts when a full file was processed.

Not getting the desiresd results especially with multiple value variables

The app doesn't opt into any support for DPI-awareness which means it's fuzzy when scaled. We need to implement the suggestions from the doc on High DPI support in Windows Forms.

It would be better if folks could just download a Windows executable (.exe) so that they don't have to compile this project. Unfortunately, I can't just post this to GitHub without proper verification and signing.

We need to work out how to get it signed properly so that it's easy for users. Ideas:

• Add release pipeline with signing.
• Publish to Windows Store, if it now support WinForms apps.