linqpad

I have a SQL CE 4.0 database on disk, and a LINQPad program that I wanted to use to fill that database. I am using the built-in (to LINQPad) linq2sql system. I am noticing that as time goes on, the time it takes to insert a batch of rows takes more and more time and eventually it looks like the program has slowed to a crawl. Is there some kind of caching or similar that is slowing it down? What, if anything, can I do to avoid this slow-down? Here's my simple test-table that I used to test this with: CREATE TABLE dummy ( id int not null primary key identity (1, 1), value nvarchar(20) not null )

In order to get results in a random order from a Sql query I generally sort by new Guids. I have done this before with Entity-Framework, however for some reason its not working now. For example (using the adventureworks2008r2 database) i run the following query in LinqPad: (from t in Employees orderby Guid.NewGuid() select new {t.Person.FirstName,t.Person.LastName,t.JobTitle}) This generates the following SQL: SELECT [t1].[FirstName], [t1].[LastName], [t0].[JobTitle] FROM [HumanResources].[Employee] AS [t0] INNER JOIN [Person].[Person] AS [t1] ON [t1].[BusinessEntityID] = [t0].

I'm trying to use LINQPad 4 (the latest beta) with Entity Framework POCO classes. I take the normal path of creating a new connection and then selecting "Entity Framework DbContext POCO(4.1) and then selecting my he assembly holding my classes. When I do so I get the following message "Could not load file or assembly EntityFramework. Version=4.1.O.O, Culture= neutral, PublicKeyToken=b77a5c561934e089 or one of its dependencies. The system cannot find the file specified." I'm able to load the assembly from my application just fine. What gives? It seems a bit different from the previous problem

What state is saved between rerunning queries in Linqpad? I presumed none, so if you run a script twice it will have the same results both time. However run the C# Program below twice in the same Linqpad tab. You'll find the first it prints an empty list, the second time a list with the message 'hey'. What's going on? System.ComponentModel.TypeDescriptor.GetAttributes(typeof(String)).OfType<ObsoleteAttribute>().Dump(); System.ComponentModel.TypeDescriptor.AddAttributes(typeof(String),new ObsoleteAttribute("hey")); LINQPad caches the application domain between queries, unless you request

Background This question got me thinking about something. Lately, since I've been looking at linq pad 's IL functionality, I've been comparing the IL code of two approaches to the same problem to "determine" which is best. Using the question linked to above, about converting an array, I generated the IL code for the two answers: var arr = new string[] { "1", "2", "3", "4" }; var result = Array.ConvertAll(arr, s => Int32.Parse(s)); produced: IL_0001: ldc.i4.4 IL_0002: newarr System.String IL_0007: stloc.2 IL_0008: ldloc.2 IL_0009: ldc.i4.0 IL_000A: ldstr "1" IL_000F: stelem.ref IL_0010: ldloc.2

I have just downloaded LinqPad to explore the benefits of using Linq queries in an application I am working on, however when I look at my database tables in the column on the left LinqPad displays all my tables with an 's' on the end, for instance CategoryTbl becomes CategoryTbls yet when I view my database in SQL management studio the table names appear correct. Though any tables that should have an S on the end ie clients remain unchanged. When I execute a Linq query I have to execute it against CategoryTbls but a SQL query has to be executed against CategoryTbl. I was just wondering why

Something of a strange question but let's see what kind of response it gets... If I code a console app (VS 2013, .NET 4.5.1) and execute this line of code: Uri.EscapeUriString("[") I get this: [ However if I execute the same thing (well, technically Uri.EscapeUriString("[").Dump() ) in LINQPad on my machine I get this: %5B To further complicate things, according to this post Uri.EscapeUriString("[") should indeed return %5B .The post was written on 27/06/2012. I'm thinking that perhaps LINQPad is referencing an older DLL than that used by VS, but that would imply that EscapeUriString has