Skip to content

Conversation

@comsemer
Copy link
Contributor

  • Added a new template and folder so that web.config can be converted outside of WebForms action
  • Added action to project.all.json corresponding to new action code in CTA

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

- Added a new template and folder so that web.config can be converted
outside of WebForms action
- Added action to project.all.json corresponding to new action code in
CTA
Copy link
Contributor

@jonlouie jonlouie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just double checking- in CTA, these actions will only execute when the project type is Web Forms?

Comment on lines 44 to 49
{
"Name": "WebFormsPorting",
"Type": "ProjectType",
"Value": "",
"Description": "Perform WebForms specific porting steps"
}
Copy link
Contributor

@jonlouie jonlouie Feb 22, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this valid if we're porting to .netstandard2.1?

.NET Standard apps are compatible with both .NET Framework and .NET Core runtimes, so my understanding here is that Blazor will not be available to apps targeting .NET Standard... but I could be wrong.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch here, after some looking it appears that .NET Standard supports Blazor WebAssembly but not Blazor Server (which we use) so I'll remove this one

@comsemer
Copy link
Contributor Author

comsemer commented Feb 22, 2022

Just double checking- in CTA, these actions will only execute when the project type is Web Forms?

@jonlouie Yes, the action checks that the project type is WebForms

- Removed action from .net standard 2.1 in project.all.json
@comsemer comsemer requested a review from jonlouie February 22, 2022 17:43
jonlouie
jonlouie previously approved these changes Feb 22, 2022
Copy link
Contributor

@jonlouie jonlouie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

Eruanion
Eruanion previously approved these changes Feb 22, 2022
},
{
"Name": "WebFormsPorting",
"Type": "ProjectType",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is ProjectType a new action type we're adding?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I added a new action type called project type. I figured WCF and any other stuff that would otherwise be used with a project rewriter could be put under this action type

marknfawaz
marknfawaz previously approved these changes Feb 22, 2022
 * These files are also used as temp tag configs in aws/cta#622
Eruanion
Eruanion previously approved these changes Mar 21, 2022
jonlouie
jonlouie previously approved these changes Mar 21, 2022
 * Asp code behind types are now correctly ...Web.UI not ...UI.Web
@comsemer comsemer dismissed stale reviews from jonlouie and Eruanion via 57e52f6 March 24, 2022 23:37
@jonlouie jonlouie requested a review from Eruanion March 24, 2022 23:42
@comsemer comsemer merged commit fa8f5e0 into master Mar 25, 2022
@comsemer comsemer deleted the comsemer-webforms-as-action branch March 25, 2022 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants