Need to not be already commonly used.
Ideally with some logical grouping.

Needed for:

• Create View
• Copy to clipboard
• Send to Toolbox
• Open Options
• Set DataContext

Add tests to ensure that structs are handled correctly

VB & C#
Copy: property, class, or selection

Change the placeholder format to reflect what's used in snippets, and avoid confusion with inline string formatting code

Add localization support for UI Text.
Initial release (1.0) will be English only.

Need to localize:

• Package level resources
• Settings dialogs
• Other UI/exception messages
• Manifest
• EULA

Version 0.1 only includes a basic profile for Xamarin.Forms apps. This is not expected to cover all scenarios and should be extended to include support for a wider range of scenarios and uses.

Please share your thoughts below.

We're actively seeking feedback on how the default profile should be changed AND any other profiles that should also be included by default.

A follow-on from #28

These will be what we ship with as the default options for launch

• UWP - basic stack panel - VM set in codebehind - C#
• UWP - basic 2Col grid - VM set in XAML - C#
• UWP - basic stack panel - VM set in codebehind - VB
• UWP - basic 2Col grid - VM set in XAML - VB
• WPF - Basic - C#
• WPF - Basic - VB
• Xamarin.Forms - Basic - C#

Need these in code and separate files in the repo too.

WPF & XF profiles included by default to show they're supported. More included by default in a future version.

Version 1.0 only includes a basic profile for WPF apps (C# & VB versions). This is not expected to cover all scenarios and should be extended to include support for a wider range of scenarios and uses.

Please share your thoughts below.

We're actively seeking feedback on how the default profile should be changed AND any other profiles that should also be included by default.

A follow-on from #28 & #71

investigation needed

If XAML is added via the clipboard or toolbox the view it's added to may still need to wire up the VM and the View. This might be in code behind or in the XAML.

Need a way of helping developers avoiding having to do this manually.

Ideas:

• Add a context menu option to the XAML view to add an entry there
• Add a context menu option to the codebehind to add an entry there (set datacontext | add VM property and initialize with new instance)
• the above context menus based on filenames
• the above context menus with VM selection from a list of options from within the project/solution
• context menu on the VM to use for initialization on a view (based on naming convention or list) -- could be in XAML or CB.

While a property binding path may require more than a property name, a nested sub-property path will likely not need/want this.
Add a configurable way to allow this.

See TODO in AnalyzerBase.cs which currently has the hardcoded removal of "ViewModel."
The simplest solution to this may be to provide a configurable value that should be removed, but it's worth exploring other possibilities.

Need to set up and establish a process for creating official releases.

This needs to handle

• build
• signing
• distribution to the VS Marketplace

Need to refine specific requirements ...

In demo project
Creating view: puts the wrong namespace in the using clause at the top of the code behind file.

It's not adjusting the source project name correctly.

Initially just create in the "/views" directory of the same project.
Configurable settings to be noted but hardcoded initially.

Must work for C# AND VB

As visual output is often minimal (just in status bar) it can be easy to miss.
Should we also provide (offer?) audible feedback too?

• This goes doubly so for errors, exceptions, or situations when no output is created.

Want to get more information about what's happening when XAML Generation goes wrong

this does work for copy to clipboard

if generating the file from solution explorer context menu.

Need to consider the naming of the file and where to put it.

Naming may involve removing/replacing a suffix from the VM file name.
Location may be the same dir, a specific dir in the same project or a different project.

Also, need to specify/configure the template of the page the content will be added to.

Need to specify how the VM is wired up to the view

• in code behind
• in the XAML

some investigation needed

Add tests for logic in options and default profiles

Original POC code only worked with a single file. This needs extending.

Needs to work with

• inherited properties in the same file
• inherited properties in another file in the same project
• inherited properties in a file in a different project
• inherited properties as native types
• inherited properties in a separate library
• classes in other files in the project
• classes in other projects in the solution
• classes of native type
• classes in other compiled library
• Getting sub-properties must work with inherited properties

Rather than generate

DataTemplate x:DataType="string">

It would be nice to instead get this:

DataTemplate x:DataType="x:String">

It will mean that more of the generated XAML will work without developer intervention.

It won't be able to do everything (e.g. custom types) but would be better than nothing.

Since moving inside a tab control

Add basic settings configuration

Need full introduction

Also be nice to have some animated gifs showing core/basic functionality.

Enable a daily (nightly) build of the VSIX and distribution via myget

Log all potential errors

especially repint without incint & nooutput

Needs to be written for a general readership

include (initially)

• sub-properties
• external libraries as base classes or types
• internal symbol access (don't have as much detail as the compiler)

Need to create the entry in https://marketplace.visualstudio.com/

Also, need to create assets and copy to accompany the listing.

X-Ref #12

Enable automated execution of tests on commit and PR.

Refine settings experience

Follow on from #15

Still outstanding (14 Dec 2018)

• invalid replacement/placeholder detection
• Remove temporary UI notice (and link)

once all outstanding actions are done verify UI against https://docs.microsoft.com/en-us/visualstudio/extensibility/ux-guidelines/evaluation-tools-for-visual-studio?view=vs-2017

Will be used for the whole project, the VSIX & future items too.

A popular question from people who've seen the early demos is "will this work with F#?"

There's no reason (AFAIK) that we couldn't do this but it's not a top priority.

In class, base class, or subproperties

Ensure 100% coverage for utility code

Investigate

• dragging files from solution explorer onto XAML code view
• dragging cs/vb code selection onto XAML code view

Same options as for #2

Ensure all UI reflects VS Theme selection.

Assigned to v1.1 as not a priority for initial launch

first need to confirm required information and assets

Hard-coded list is sufficient initially.

For MVVMLight want to exclude IsInDesignMode
check other frameworks for similar

Export as JSON with a ".rxprofile" extension.
Importing must handle errors and report any issues.

Also, host default profile files in the repository.

Rather than default to a profile if none are selected, ask the user to choose one when first using the extension.

Context menus should not include functionality options when no profile is active. Instead, they should point to the settings (including a link) and require a profile be set to active.

Settings dialog should make clear if no profile is active and prompt to select one.

Need icons for

• Copy to clipboard
• Send to Toolbox
• Create View
• Open Options
• Set Datacontext

Add documentation of tests that must be done manually.

For anything that can't be done in an automated way (X-Ref #9)

public ObservableCollection<string> Items { get; set; } currently produces

            <ListView ItemsSource="{x:Bind ViewModel.Items}">
                <ListView.ItemTemplate>
                    <DataTemplate x:DataType="x:String">
                        <StackPanel>
                            <TextBlock Text="{x:Bind Items}" />
                        </StackPanel>
                    </DataTemplate>
                </ListView.ItemTemplate>
            </ListView>

It uses the fallback name of the sub-property entry.
But this isn't valid.

The sub-prop should be

<TextBlock Text="{x:Bind }" />

Required for #18

From original POC TODO
Also, add the ability to log errors to output window or details output to a custom output window. See https://stackoverflow.com/questions/1094366/how-do-i-write-to-the-visual-studio-output-window-in-my-custom-tool

Add a platform agnostic analyzer that checks for the use of different aliases for the same namespace in different files within the project (solution?)

Using consistent aliases throughout a codebase aids maintainability.

Currently set to true to encourage the capture of more error issues during early testing.