You searched for the word(s): userid:713146

More Search Options

RSS Available

• GridViews are not so wonderful

  Much of the "press" about the GridView revolves around how "it is a great improvement over the DataGrid" and how it contains so much inbuilt functionality. Maybe I am missing something, as I am not professing to be an expert in .NET but if the GridView is so great, why do the following appear to be true when using a GridView with an ObjectDataSource: 1) It takes a major workaround involving the addition and hiding of a "dummy" blank row to get the GridView to display

  Posted to Data Access and ObjectDataSource Control (Forum) by arcology on 10/31/2007
  Filed under: Gridview DataGrid

• Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

  OK, I think I have found the solution. The problem appears to be entirely to do with the format of the connection string which somehow appears in the "new" .XSD version. My old connections string of the form: <Connection AppSettingsObjectName="Settings" AppSettingsPropertyName="ArcTimeConnectionString" ConnectionStringObject="" IsAppSettingsProperty="True" Modifier="Assembly" Name="ArcTimeConnectionString (Settings)" ParameterPrefix="@" PropertyReference="ApplicationSettings.ArcTime.Properties

  Posted to Visual Studio 2005 (Forum) by arcology on 3/14/2007
  Filed under: Web Config setting, ASP.net 2.0, MSDataSetGenerator, Web Applications

• Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

  So Jason, you are of the opinion that it is the Graphical tool screwing up the .XSD rather than the MSDataSetGenerator not producing a correct C# dataset class from the .XSD? Thing is, I made a change by adding a new "Query" to the TableAdaptor (which broke Dataset designer/MSDataSetGenerator) and using VSS compared the before and after files. No changes were made to the .XSD file other than the definition for the added query and the ConnectionString change which I had to make (prefixing old name

  Posted to Visual Studio 2005 (Forum) by arcology on 3/13/2007
  Filed under: ASP.NET, datasets, MSDataSetGenerator, Web Applications

• Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

  I am having exactly the same problem. I can't believe that VS 2005 SP1 can have completely broken typed datasets (.XSDs) for all development sites!? So why are so few people reporting it and there seems to be no awareness of it at Microsoft? Either that or there really are a very small number of sites who are: a) Using VS 2005 SP1 b) Using typed datasets c) Have needed to make a change post install of SP1 Did you find a solution yet? When you say you manually edited the xml to continue, what did

  Posted to Visual Studio 2005 (Forum) by arcology on 3/13/2007
  Filed under: Tabladapters SP1 WebApplication Project Connectionstring, VS 2005, ASP.NET, datasets