-
Notifications
You must be signed in to change notification settings - Fork 12
Added WebForms appsettings template and action #137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- 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
jonlouie
left a comment
There was a problem hiding this 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?
recommendation/project.all.json
Outdated
| { | ||
| "Name": "WebFormsPorting", | ||
| "Type": "ProjectType", | ||
| "Value": "", | ||
| "Description": "Perform WebForms specific porting steps" | ||
| } |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
@jonlouie Yes, the action checks that the project type is WebForms |
- Removed action from .net standard 2.1 in project.all.json
jonlouie
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
| }, | ||
| { | ||
| "Name": "WebFormsPorting", | ||
| "Type": "ProjectType", |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
* These files are also used as temp tag configs in aws/cta#622
0b35c0c
* Asp code behind types are now correctly ...Web.UI not ...UI.Web
…net-datastore into comsemer-webforms-as-action
* Added test
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.