How to modify following default behavior?

4 posts, 0 answers
  1. Jin
    Jin avatar
    80 posts
    Member since:
    Jun 2012

    Posted 23 Aug 2012 Link to this post

    How to modify following default behavior?

    1.When creating a Domain Model, it will let your to type a file name for example "MyModule.rlinq". Then it will switch to another window to type some information. At this time, it will have a textbox to type module name. My concern is that whether there is a way to display the file name as default text instead of EntitiesModel because most scenario is that the file name is the same with module name.

    2.When I creating a Domain Model first time, it will create a connection string in App.config, then I create another Domain Module, it will auto create another connection string instead of selecting an existing one. 

    3.Whether there is a way to select an connecting string from a configuration file under one project? If my project have three modules which will have three entity projects to map every module.The connecting string is put under web application project. As current situation, when creating Domain module, it will create mutipule connection string in three projects. If I change the connection  string
    , all related connection string will be modified. Whether there is a way to select the connection string from the web.config under web applicaiton project?
  2. Zoran
    Admin
    Zoran avatar
    534 posts

    Posted 27 Aug 2012 Link to this post

    Hi Jin,

    I agree that your proposals under #1 and #2 do make sense and they are already in our internal team portal for further discussions within our team which would lead to a decision if the default behavior will be changed or not. The current default behavior is based on certain decision which were made because of some restrictions in the first versions of the Visual Designer, but they will be re-discussed following your request. At the moment, none of the current default behaviors can't be changed/configured with the actual version that you have installed at the moment.

    As for request #3, this is something i am afraid can't be changed at this stage. The reason for this is the fact that the Visual Designer requires a connection string during design-time in order to have access to the database. That connection string must be in the same project as the .rlinq file as it is not so straight-forward to traverse the whole solution for connection strings during design time. During runtime however, you can remove all configuration file which you feel unnecessary and leave only one connection string in your actual executing project, a Web or Win Forms/WPF application.

     

    Greetings,
    Zoran
    the Telerik team
    Follow @OpenAccessORM Twitter channel to be the first one to get the latest updates on new releases, tips and tricks and sneak peeks at our product labs!
  3. DevCraft banner
  4. Jin
    Jin avatar
    80 posts
    Member since:
    Jun 2012

    Posted 28 Aug 2012 Link to this post

    For request #3, if we have a way to select one existing connection string name from dropdownlist, I can put one App.config under common project and other project add that App.config as a link, so other project will all refer the same connection string.
  5. Zoran
    Admin
    Zoran avatar
    534 posts

    Posted 31 Aug 2012 Link to this post

    Hello Jin,

     We will evaluate this proposal as well, we just need to make a bit of a research about how easy and reliable is to access the connection string from linked files during design time.

    Greetings,
    Zoran
    the Telerik team
    Follow @OpenAccessORM Twitter channel to be the first one to get the latest updates on new releases, tips and tricks and sneak peeks at our product labs!
Back to Top