You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-commits@incubator.apache.org by "Lars Corneliussen (Created) (JIRA)" <ji...@apache.org> on 2011/11/08 16:09:51 UTC
[jira] [Created] (NPANDAY-479) Refactor Visual Studio Add-in to
some more developer-friendlyness
Refactor Visual Studio Add-in to some more developer-friendlyness
-----------------------------------------------------------------
Key: NPANDAY-479
URL: https://issues.apache.org/jira/browse/NPANDAY-479
Project: NPanday
Issue Type: Improvement
Components: Visual Studio Add-in
Reporter: Lars Corneliussen
Assignee: Lars Corneliussen
Fix For: 1.4.1-incubating
The Addin code is a three-files-monster. For the sake of maintainability and testability it needs to be refactored a bit.
# Introduce the command pattern (One class per Command)
# Make commands call other commands
# Factor out event-receivers in one class each
# ...
I also use it to learn to understand the Addin code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-479) Refactor Visual Studio Add-in + .NET
modules to some more developer-friendlyness
Posted by "Lars Corneliussen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen updated NPANDAY-479:
--------------------------------------
Description:
The Addin code is a three-files-monster. And most of the .NET-code looks quite ugly :-)
For the sake of maintainability and testability it needs to be refactored a bit.
# (/) Introduce the command pattern (One class per Command)
# (/) Create a Debug-output pane for SNAPSHOTS
# (/) Create a master-solution including all projects and test projects
# Update the documentation (provide new solution path) and delete the old solution under assemblies/NPanday ?
# (/) One class per file
# Omit folders for root namespace (example: NPanday/Model/Settings is not needed, if the Default Namespace is NPanday.Model.Settings; it's not java! :-))
...
I also use it to learn to understand the Addin code.
was:
The Addin code is a three-files-monster. And most of the .NET-code looks quite ugly :-)
For the sake of maintainability and testability it needs to be refactored a bit.
# (/) Introduce the command pattern (One class per Command)
# Make commands call other commands
# Factor out event-receivers in one class each
# (/) Create a Debug-output pane for SNAPSHOTS
# Refactor all Console.WriteLines and OutputPane.OutputString to use the logger (which writes to the Output pane)
# (/) Create a master-solution including all projects and test projects
# Update the documentation (provide new solution path) and delete the old solution under assemblies/NPanday ?
# (/) One class per file
# Omit folders for root namespace (example: NPanday/Model/Settings is not needed, if the Default Namespace is NPanday.Model.Settings; it's not java! :-))
...
I also use it to learn to understand the Addin code.
> Refactor Visual Studio Add-in + .NET modules to some more developer-friendlyness
> --------------------------------------------------------------------------------
>
> Key: NPANDAY-479
> URL: https://issues.apache.org/jira/browse/NPANDAY-479
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Reporter: Lars Corneliussen
> Assignee: Lars Corneliussen
> Fix For: 1.4.1-incubating
>
>
> The Addin code is a three-files-monster. And most of the .NET-code looks quite ugly :-)
> For the sake of maintainability and testability it needs to be refactored a bit.
> # (/) Introduce the command pattern (One class per Command)
> # (/) Create a Debug-output pane for SNAPSHOTS
> # (/) Create a master-solution including all projects and test projects
> # Update the documentation (provide new solution path) and delete the old solution under assemblies/NPanday ?
> # (/) One class per file
> # Omit folders for root namespace (example: NPanday/Model/Settings is not needed, if the Default Namespace is NPanday.Model.Settings; it's not java! :-))
> ...
> I also use it to learn to understand the Addin code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-479) Refactor Visual Studio Add-in + .NET
modules to some more developer-friendlyness
Posted by "Lars Corneliussen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen updated NPANDAY-479:
--------------------------------------
Description:
The Addin code is a three-files-monster. And most of the .NET-code looks quite ugly :-)
For the sake of maintainability and testability it needs to be refactored a bit.
# (/) Introduce the command pattern (One class per Command)
# Make commands call other commands
# Factor out event-receivers in one class each
# (/) Create a Debug-output pane for SNAPSHOTS
# Refactor all Console.WriteLines and OutputPane.OutputString to use the logger (which writes to the Output pane)
# (/) Create a master-solution including all projects and test projects
# Update the documentation (provide new solution path) and delete the old solution under assemblies/NPanday ?
# (/) One class per file
# Omit folders for root namespace (example: NPanday/Model/Settings is not needed, if the Default Namespace is NPanday.Model.Settings; it's not java! :-))
...
I also use it to learn to understand the Addin code.
was:
The Addin code is a three-files-monster. For the sake of maintainability and testability it needs to be refactored a bit.
# (/) Introduce the command pattern (One class per Command)
# Make commands call other commands
# Factor out event-receivers in one class each
# (/) Create a Debug-output pane for SNAPSHOTS
# Refactor all Console.WriteLines and OutputPane.OutputString to use the logger (which writes to the Output pane)
# (/) Create a master-solution including all projects and test projects
# Update the documentation (provide new solution path) and delete the old solution under assemblies/NPanday ?
# ...
I also use it to learn to understand the Addin code.
Summary: Refactor Visual Studio Add-in + .NET modules to some more developer-friendlyness (was: Refactor Visual Studio Add-in to some more developer-friendlyness)
> Refactor Visual Studio Add-in + .NET modules to some more developer-friendlyness
> --------------------------------------------------------------------------------
>
> Key: NPANDAY-479
> URL: https://issues.apache.org/jira/browse/NPANDAY-479
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Reporter: Lars Corneliussen
> Assignee: Lars Corneliussen
> Fix For: 1.4.1-incubating
>
>
> The Addin code is a three-files-monster. And most of the .NET-code looks quite ugly :-)
> For the sake of maintainability and testability it needs to be refactored a bit.
> # (/) Introduce the command pattern (One class per Command)
> # Make commands call other commands
> # Factor out event-receivers in one class each
> # (/) Create a Debug-output pane for SNAPSHOTS
> # Refactor all Console.WriteLines and OutputPane.OutputString to use the logger (which writes to the Output pane)
> # (/) Create a master-solution including all projects and test projects
> # Update the documentation (provide new solution path) and delete the old solution under assemblies/NPanday ?
> # (/) One class per file
> # Omit folders for root namespace (example: NPanday/Model/Settings is not needed, if the Default Namespace is NPanday.Model.Settings; it's not java! :-))
> ...
> I also use it to learn to understand the Addin code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (NPANDAY-479) Refactor Visual Studio Add-in
to some more developer-friendlyness
Posted by "Lars Corneliussen (Work started) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on NPANDAY-479 started by Lars Corneliussen.
> Refactor Visual Studio Add-in to some more developer-friendlyness
> -----------------------------------------------------------------
>
> Key: NPANDAY-479
> URL: https://issues.apache.org/jira/browse/NPANDAY-479
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Reporter: Lars Corneliussen
> Assignee: Lars Corneliussen
> Fix For: 1.4.1-incubating
>
>
> The Addin code is a three-files-monster. For the sake of maintainability and testability it needs to be refactored a bit.
> # Introduce the command pattern (One class per Command)
> # Make commands call other commands
> # Factor out event-receivers in one class each
> # ...
> I also use it to learn to understand the Addin code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-479) Refactor Visual Studio Add-in + .NET
modules to some more developer-friendlyness
Posted by "Lars Corneliussen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen updated NPANDAY-479:
--------------------------------------
Description:
The Addin code is a three-files-monster. And most of the .NET-code looks quite ugly :-)
For the sake of maintainability and testability it needs to be refactored a bit.
# (/) Introduce the command pattern (One class per Command)
# (/) Create a Debug-output pane for SNAPSHOTS
# (/) Create a master-solution including all projects and test projects
# (/) Update the documentation (provide new solution path) and delete the old solution under assemblies/NPanday ?
# (/) One class per file
# (/) Omit folders for root namespace (example: NPanday/Model/Settings is not needed, if the Default Namespace is NPanday.Model.Settings; it's not java! :-))
...
I also use it to learn to understand the Addin code.
was:
The Addin code is a three-files-monster. And most of the .NET-code looks quite ugly :-)
For the sake of maintainability and testability it needs to be refactored a bit.
# (/) Introduce the command pattern (One class per Command)
# (/) Create a Debug-output pane for SNAPSHOTS
# (/) Create a master-solution including all projects and test projects
# Update the documentation (provide new solution path) and delete the old solution under assemblies/NPanday ?
# (/) One class per file
# Omit folders for root namespace (example: NPanday/Model/Settings is not needed, if the Default Namespace is NPanday.Model.Settings; it's not java! :-))
...
I also use it to learn to understand the Addin code.
> Refactor Visual Studio Add-in + .NET modules to some more developer-friendlyness
> --------------------------------------------------------------------------------
>
> Key: NPANDAY-479
> URL: https://issues.apache.org/jira/browse/NPANDAY-479
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Reporter: Lars Corneliussen
> Assignee: Lars Corneliussen
> Fix For: 1.4.1-incubating
>
>
> The Addin code is a three-files-monster. And most of the .NET-code looks quite ugly :-)
> For the sake of maintainability and testability it needs to be refactored a bit.
> # (/) Introduce the command pattern (One class per Command)
> # (/) Create a Debug-output pane for SNAPSHOTS
> # (/) Create a master-solution including all projects and test projects
> # (/) Update the documentation (provide new solution path) and delete the old solution under assemblies/NPanday ?
> # (/) One class per file
> # (/) Omit folders for root namespace (example: NPanday/Model/Settings is not needed, if the Default Namespace is NPanday.Model.Settings; it's not java! :-))
> ...
> I also use it to learn to understand the Addin code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-479) Refactor Visual Studio Add-in to
some more developer-friendlyness
Posted by "Lars Corneliussen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen updated NPANDAY-479:
--------------------------------------
Description:
The Addin code is a three-files-monster. For the sake of maintainability and testability it needs to be refactored a bit.
# (/) Introduce the command pattern (One class per Command)
# Make commands call other commands
# Factor out event-receivers in one class each
# (/) Create a Debug-output pane for SNAPSHOTS
# Refactor all Console.WriteLines and OutputPane.OutputString to use the logger (which writes to the Output pane)
# (/) Create a master-solution including all projects and test projects
# Update the documentation (provide new solution path) and delete the old solution under assemblies/NPanday ?
# ...
I also use it to learn to understand the Addin code.
was:
The Addin code is a three-files-monster. For the sake of maintainability and testability it needs to be refactored a bit.
# (/) Introduce the command pattern (One class per Command)
# Make commands call other commands
# Factor out event-receivers in one class each
# (/) Create a Debug-output pane for SNAPSHOTS
# Refactor all Console.WriteLines and OutputPane.OutputString to use the logger (which writes to the Output pane)
# ...
I also use it to learn to understand the Addin code.
> Refactor Visual Studio Add-in to some more developer-friendlyness
> -----------------------------------------------------------------
>
> Key: NPANDAY-479
> URL: https://issues.apache.org/jira/browse/NPANDAY-479
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Reporter: Lars Corneliussen
> Assignee: Lars Corneliussen
> Fix For: 1.4.1-incubating
>
>
> The Addin code is a three-files-monster. For the sake of maintainability and testability it needs to be refactored a bit.
> # (/) Introduce the command pattern (One class per Command)
> # Make commands call other commands
> # Factor out event-receivers in one class each
> # (/) Create a Debug-output pane for SNAPSHOTS
> # Refactor all Console.WriteLines and OutputPane.OutputString to use the logger (which writes to the Output pane)
> # (/) Create a master-solution including all projects and test projects
> # Update the documentation (provide new solution path) and delete the old solution under assemblies/NPanday ?
> # ...
> I also use it to learn to understand the Addin code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-479) Refactor Visual Studio Add-in to
some more developer-friendlyness
Posted by "Lars Corneliussen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen updated NPANDAY-479:
--------------------------------------
Description:
The Addin code is a three-files-monster. For the sake of maintainability and testability it needs to be refactored a bit.
# (/) Introduce the command pattern (One class per Command)
# Make commands call other commands
# Factor out event-receivers in one class each
# (/) Create a Debug-output pane for SNAPSHOTS
# Refactor all Console.WriteLines and OutputPane.OutputString to use the logger (which writes to the Output pane)
# ...
I also use it to learn to understand the Addin code.
was:
The Addin code is a three-files-monster. For the sake of maintainability and testability it needs to be refactored a bit.
# Introduce the command pattern (One class per Command)
# Make commands call other commands
# Factor out event-receivers in one class each
# ...
I also use it to learn to understand the Addin code.
> Refactor Visual Studio Add-in to some more developer-friendlyness
> -----------------------------------------------------------------
>
> Key: NPANDAY-479
> URL: https://issues.apache.org/jira/browse/NPANDAY-479
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Reporter: Lars Corneliussen
> Assignee: Lars Corneliussen
> Fix For: 1.4.1-incubating
>
>
> The Addin code is a three-files-monster. For the sake of maintainability and testability it needs to be refactored a bit.
> # (/) Introduce the command pattern (One class per Command)
> # Make commands call other commands
> # Factor out event-receivers in one class each
> # (/) Create a Debug-output pane for SNAPSHOTS
> # Refactor all Console.WriteLines and OutputPane.OutputString to use the logger (which writes to the Output pane)
> # ...
> I also use it to learn to understand the Addin code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-479) Refactor Visual Studio Add-in +
.NET modules to some more developer-friendlyness
Posted by "Lars Corneliussen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen resolved NPANDAY-479.
---------------------------------------
Resolution: Fixed
More to be done in NPANDAY-481
> Refactor Visual Studio Add-in + .NET modules to some more developer-friendlyness
> --------------------------------------------------------------------------------
>
> Key: NPANDAY-479
> URL: https://issues.apache.org/jira/browse/NPANDAY-479
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Reporter: Lars Corneliussen
> Assignee: Lars Corneliussen
> Fix For: 1.4.1-incubating
>
>
> The Addin code is a three-files-monster. And most of the .NET-code looks quite ugly :-)
> For the sake of maintainability and testability it needs to be refactored a bit.
> # (/) Introduce the command pattern (One class per Command)
> # (/) Create a Debug-output pane for SNAPSHOTS
> # (/) Create a master-solution including all projects and test projects
> # (/) Update the documentation (provide new solution path) and delete the old solution under assemblies/NPanday ?
> # (/) One class per file
> # (/) Omit folders for root namespace (example: NPanday/Model/Settings is not needed, if the Default Namespace is NPanday.Model.Settings; it's not java! :-))
> ...
> I also use it to learn to understand the Addin code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira