CSS missing on server

Posted by: jason.brandt on 7 September 2018, 8:40 am EST

  • Posted 7 September 2018, 8:40 am EST

    I am using VS2017 to deploy all content to a server.

    When viewing the website built on the server, flexgrid has different/missing CSS than on localhost

    In addition, some features are not working properly on the grid (such as column sort and advanced filters column filter menu.

    What are some reasons why these files would differ?

    Is there a process to get wijmo to build its TS through VS2017?

  • Posted 9 September 2018, 7:22 pm EST

    Hi Jason,

    Could you please tell us more about which files are different/missing?

    Also could you please provide some more info about your project config like:

    •Is it a simple web project or an MVC or Web Form application

    •Are you using any frameworks like angular, react, vue

    •Are you using CDN to refer to any of the Wijmo files

    •Are you using any module bundler? If yes, which one

    •Is the deploying server an IIS server or a node server

    •Is the server using HTTPS or HTTP protocol

    •Can you please share the server config file?

    •If using modules, then which Wijmo build are you using ex: systemjs,amd or commonjs.

    •How are you referring to the Wijmo build

    Thanks

    Sharad

  • Posted 10 September 2018, 3:55 am EST

    •Is it a simple web project or an MVC or Web Form application

    - It is a MVC application using microsoft server and TFS for code repository

    •Are you using any frameworks like angular, react, vue

    - We are using AngularJS as host of main web app , and then in this page we have upgraded to Angular 2+ and are hosting Wijmo in Angular 2+ sections

    •Are you using CDN to refer to any of the Wijmo files

    - No, all files are contained in the web directory directly

    •Are you using any module bundler? If yes, which one

    - No, we are not using bundling at this time

    •Is the deploying server an IIS server or a node server

    - Yes we are deploying to IIS server remotely via TFS auto build functionality



    •Is the server using HTTPS or HTTP protocol

    - This is for intranet, so the site uses HTTP

    •Can you please share the server config file?

    • Config File =
    {
      "compilerOptions": {
        "target": "es5",
        "module": "amd",
        "moduleResolution": "node",
        "sourceMap": true,
        "emitDecoratorMetadata": true,
        "experimentalDecorators": true,
        "lib": [ "es6", "dom" ],
        "removeComments": false,
        "noImplicitAny": false,
        "suppressImplicitAnyIndexErrors": true,
        "outDir": "dist",
        "rootDir": ".",
        "typeRoots": [
          "./node_modules/@types"
        ],
        "types": []//this is to ignore the types node folder
      },
      "exclude": [
        "node_modules",
        "NpmImages", // I noticed this here, but am not sure why it is in excludes for tsc build... 
        "packages"
      ]
    }
    

    •If using modules, then which Wijmo build are you using ex: systemjs,amd or commonjs.

    - We are using wijmo-amd-min files

    •How are you referring to the Wijmo build

    - We are referencing them in the config files for each module in the mpa object as : ‘wijmo’: global.baseUrl + ‘/node_modules/wijmo’,

    - and in the json package file as “wijmo”: “file:NpmImages/wijmo-amd-min”,

  • Posted 10 September 2018, 3:57 am EST

    If I remove the wijmo items from the Exclude section in the tsconfig file and do a tsc (typescript compile) I get the following error on build =

    
    NpmImages/wijmo-amd-min/wijmo.d.ts(417,22): error TS2420: Class 'ObservableArray' incorrectly implements interface 'INotifyCollectionChanged'.
      Types of property 'collectionChanged' are incompatible.
        Type 'Event' is not assignable to type 'Event'. Two different types with this name exist, but they are unrelated.
          Types have separate declarations of a private property '_handlers'.
    NpmImages/wijmo-amd-min/wijmo.d.ts(440,22): error TS2420: Class 'CollectionView' incorrectly implements interface 'IEditableCollectionView'.
      Types of property 'currentChanged' are incompatible.
        Type 'Event' is not assignable to type 'Event'. Two different types with this name exist, but they are unrelated.
    NpmImages/wijmo-amd-min/wijmo.d.ts(440,22): error TS2420: Class 'CollectionView' incorrectly implements interface 'IPagedCollectionView'.
      Types of property 'pageChanged' are incompatible.
        Type 'Event' is not assignable to type 'Event'. Two different types with this name exist, but they are unrelated.
    NpmImages/wijmo-amd-min/wijmo.react.base.d.ts(1,23): error TS2688: Cannot find type definition file for 'react'.
    NpmImages/wijmo-amd-min/wijmo.react.base.d.ts(2,24): error TS2307: Cannot find module 'react'.
    NpmImages/wijmo-amd-min/wijmo.react.input.d.ts(1,23): error TS2688: Cannot find type definition file for 'react'.
    NpmImages/wijmo-amd-min/wijmo.react.input.d.ts(3,24): error TS2307: Cannot find module 'react'.
    NpmImages/wijmo-amd-min/wijmo.viewer.d.ts(1892,22): error TS2415: Class 'ReportViewer' incorrectly extends base class 'ViewerBase'.
      Types of property '_createPage' are incompatible.
        Type '(index: number, defPageSize: _ISize) => _Page' is not assignable to type '(index: number, defPageSize: _ISize) => _Page'. Two different types with this name exist, but they are unrelated.
          Type '_Page' is not assignable to type '_Page'. Two different types with this name exist, but they are unrelated.
            Types have separate declarations of a private property '_documentSource'.
    node_modules/wijmo/wijmo.react.base.d.ts(1,23): error TS2688: Cannot find type definition file for 'react'.
    node_modules/wijmo/wijmo.react.base.d.ts(2,24): error TS2307: Cannot find module 'react'.
    
  • Posted 10 September 2018, 4:03 am EST

    Also note =

    When updating to latest version of Wijmo I simply did a full overwrite of the wijmo-amd-min folder and its contents as well as the content folder for styles.

    This made my local code update to latest and display correctly, but this does not propagate to server when TFS gets the files.

    As well, it now shows the wijmo Evaluation Version warning even though we have a registered copy…

  • Posted 10 September 2018, 4:23 am EST

    Lastly, Manual copy of the wijmo-amd-min folder to remote server folder has solved this issue.

    Why do the files not copy over when typescript is compiled?

  • Posted 10 September 2018, 10:14 pm EST

    Hi,

    We are sorry for the inconvenience.

    First of all, you need not compile Wijmo file since we provide compiled files as you are using wijmo-amd-min.

    .

    This made my local code update to latest and display correctly, but this does not propagate to server when TFS gets the files.

    Thanks for notifying us that you have been able to resolve this issue using manual. The reason behind this may be as following:

    The previous build folder do not get deleted or update command is not executed successfully.

    As well, it now shows the wijmo Evaluation Version warning even though we have a registered copy…

    It seems you are using builds prior to 5.20181.436. If yes, then licensing mechanism has been changed from build 5.20181.436.

    Please refer to the following blog:

    https://www.grapecity.com/en/blogs/how-to-deploy-a-wijmo-app-with-new-licensing

    Please let us know if you have any further queries.

    ~Manish

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels