Skip to content

Include options for type and solution in the docs  #10

@d4hines

Description

@d4hines

I'd like to thank you for making this - it fills a pretty big whole in the client-side development flow, and will save a lot of time.
Two points about the documentation though:

  • It's never made clear that you have to specify the resource type in the config if you want to create a new web resource. Omitting the type causes an exception from the Web API.
  • It's also never made clear that you can specify a Solution for it to be added to.

The example config
on lines 43-46, of the README.md:

    WebResources:[
     { Path:'TestWebResource\\TestWebResource1.js',UniqueName:'ctc_TestWebResource1.js' },
     { Path:'TestWebResource\\TestWebResource2.js',UniqueName:'ctc_TestWebResource2.js' },
    ]

Should read something like

{ 
  Path:'TestWebResource\\TestWebResource1.js',
  UniqueName:'ctc_TestWebResource1.js',
  Type: 'JavaScript',
  Solution: 'MySolution'
}
...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions