Tech Off Thread

8 posts

VS2008: Linq to Sql Show stopper? [C#: Resolved]

Back to Forum: Tech Off
  • User profile image
    Secret​Software

    Hi,
        I think there is something wrong with Linq to sql.

    1) Try to drag and drop 50 + Stored procedure at the same time on the LINQ To SQL designer.

    2) Say no to the prompt window that asks you to save sensitive data pertaining to the connection string to the sql db.


    result.

    All the stored procedures appear in the methods of the LINQ to SQL design surface, but in the DataContex cs , file that is auto generated, nothing is written in code that has to do with the dropped stored procedures.

    Why?Expressionless


    PS: this works, only if I drag and drop them 1 at a time or 2 at a time. But not all to gether. Why?Mad

  • User profile image
    PeterF

    why showstopper when you have a perfect workaround? btw why would you add all 50 at once? don't you loose overview like that?

  • User profile image
    Secret​Software

    PeterF wrote:
    why showstopper when you have a perfect workaround? btw why would you add all 50 at once? don't you loose overview like that?


    Actually, even if you do it one by one, it stops after you ad the 10th sp.

    Weird bug.

    Not sure how to fix.

    Reason to add all, at once, is because its faster that way.

    No one has the time to add them one by one.

    Common man.Wink

    If you add them all, one by one, and try to run the custome tool, you get lots of weird errors.


    LINQ TO SQL is broken in VS 2008.Mad:@Mad:@Mad

    [C]


  • User profile image
    PeterF

    Is it always stopping at the same stored procedure?

    List the stored procedures so people can repro it.

  • User profile image
    Secret​Software

    PeterF wrote:
    

    Is it always stopping at the same stored procedure?



    No. Sometimes, if you clear the design surface, and readd them one by one, only the first one you add gets coded in the xx.designer.cs file.

    The weird thing is that in the designer it shows as added, with method signature, but not in the cs file. The autogen tool is not working.


    PeterF wrote:
    

    List the stored procedures so people can repro it.



    I cant list them.

    This happens when you try to run custom tool.

    Error    1    Build failed due to validation errors in C:\Users\xxx\Documents\Visual Studio 2008\Projects\...\XXDb.dbml.  Open the file and resolve the issues in the Error List, then try rebuilding the project.  


    Error    2    Required file 'alink.dll with IAlink3' could not be found    xxx

    Error    3    Could not load type 'System.ComponentModel.PropertyChangingEventArgs' from assembly 'System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxx'.        0    0 


    xx = to hide private data.


    This really is annoying. Its happening at randomal drag and drops.

    sometimes it works , sometimes it does not.

    Not SP specific.



  • User profile image
    PeterF

    In the mean time go to help->report a bug.

  • User profile image
    Secret​Software

    Well i just discovered that this bug existed back since Beta 1 of Orcas.

    The fix for it exists in the Installation DVD, however the installer never invokes the update. So you kind of have to do it manually.

    You cannot build any application because of the missing alink.dll.

    So to fix.

    Install these msu files that are located off of the install image in

    WCU\dotNetFramework\dotNetMSP\x86.

    • Windows6.0-KB110806-x86.msu
    • Windows6.0-KB929300-x86.msu
    • Windows6.0-kb930264-x86.msu

    Everything worked fine afterwards



    They might have different names, but the KB #s are the same.



    Thanks


  • User profile image
    bitdisaster

    SecretSoftware wrote:
    Well i just discovered that this bug existed back since Beta 1 of Orcas.

    The fix for it exists in the Installation DVD, however the installer never invokes the update. So you kind of have to do it manually.

    You cannot build any application because of the missing alink.dll.

    So to fix.

    Install these msu files that are located off of the install image in

    WCU\dotNetFramework\dotNetMSP\x86.

    • Windows6.0-KB110806-x86.msu
    • Windows6.0-KB929300-x86.msu
    • Windows6.0-kb930264-x86.msu

    Everything worked fine afterwards



    They might have different names, but the KB #s are the same.



    Thanks




    I had also trouble with these patches. Actually they are installed while the setup process, but sometime they don't. Check your event log and you will find related errors. In my case no of the Designer works. (WinForms, WPF).

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.