Well contrary to the common notion, the Neo of the real life Matrix might be a physicist. According to the latest research it is starting to look like there is a significant chance that we might be living inside a universe which is basically a simulation or some sort of a hologram.
I am pretty sure that any web developer would hate an exception that is hard to catch. One of those is the one which says “The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>).”
In my case I got this exception on a page that was working perfectly about two days ago and now had been untouched since then. My first line of Googling defense resulted in articles like this article and other discussions that tell you to change the <%= xxxxx %> to <%# xxxxx %>. Below I show how my code was when I was getting the error.
However just changing the <%= sign to <%# or moving the script tag within the content placeholder did not make any difference because even though it removed the original issue but caused another problem. The JavaScript wouldn’t load. :S
Here is my solution that resolves the issue and still lets the JavaScript load.
Just inject the script tag in a literal in the head of the master page in the code behind.
The sample below shows how to convert time from one time zone (say local) to another time zone (say Arizona time)
DateTime dlocal
= DateTime.Now;
DateTime dNonLocal
= TimeZoneInfo.ConvertTime(
dlocal,
TimeZoneInfo.FindSystemTimeZoneById("US Mountain Standard Time"));
Another real-good article on TimeZoneInfo class can be found here.
Recently when I was using LINQ to SQL (which I happen to love so much) and using the LINQ to SQL debug visualizer tool (which can be found here) to see what query was getting generated I came across an issue. below is a screen-shot of the query I was looking at.
If I inspected it in the quick-watch window, everything was fine. I get one member in my results collection.
However, when I look it up in the LINQ to SQL debug visualizer window, the SQL statement that is shown is not right. I see that the string parameter in that statement has not been enclosed in quotes. And hence when I click the execute button I get an exception.
So it goes to show that there is an issue in the visualizer even though the actual query seems to run perfectly fine.
I also saw a post regarding this behavior on the LINQ Project Forum and my advice to the people who have had this issue to keep the above issue in mind while debugging.
Make sure that you put permissions for the user you are logging in with, in the permissions file (the AuthSVNAccessFile). Make sure this user has permissions for the repository you are trying to checkout.
For example, to grant Harry read+write privilages to the repository called “MyRepositoryName”, the file should look like below.
[MyRepositoryName:/]
Harry = rw
I got this error when I was trying to configure Subversion with Apache on Windows XP. There seem to be many people on Google who have this issue. This is my first time when I am installing these together so something that I noted might be trivial but at the same time I believe that it’s really easy to miss. Since I am mostly developing on IIS I need that to run on the default ports and hence have Apache running on a different ports. The point is not to forget to use the port (on which Apache is running) in the URL used while referring to the Subversion.
When I hear about millions losing jobs due to the global economic recession that is plaguing the world these days, I find myself thinking about everyone who lost his or her job and how would the life be for that person. How would that person survive in the coming months ? More so, if that person has a family. What will happen if a family runs out of money, worst if it runs out of credit. What will happen if someone is not able to find a meal at the end of the day. Those are some really bad thoughts I have sometimes. What makes them horrible that they might actually come true. All I can do is to dismiss them in a hope that the situation will improve. The stimulus package will work and slowly people will find the jobs they are looking for.
There are some things that we might need to consider when it comes to us having putting up our expectations from the coming months. One of the most important is that everyone wants to save money: Businesses being in the front row. Second thing to consider is that our world is becoming more and more connected by the day and these connections are becoming cheaper as we speak(god bless the market competition). Globalization is the name of the game. Planning and designing in one country, produce and package in another, shipping and delivering from yet another. That is how profit is achieved in the fiercely competitive and global markets in these times.
When and if governments start imposing restrictions on the way businesses operate, business owners are left with no options but to close down or to resort to work around these restrictions because if there is no profit there cannot be business. If a business can get a product’s raw materials and build it at a different location from the country in which the product is sold at a significant profit: That is the way the business will operate. If that is not an option, business will seek the next most profitable option. However, if the only edge that made the business prosper was the profit that it was gaining out of production in a different country, choosing the second option would not be possible. That will just drive the business out of profit and out of picture. This, I think, will be the fate of a lot of businesses, if governments start imposing country specific restrictions on different businesses.
What needs to be done however is that, going forward, projects and businesses that cannot afford to lose profits are need based and not greed based. The meaning of this is that a project or a business is started because people really need something that the business produces (a commodity) not what would have been a “good to have” something (a luxury). If we look specifically at sectors like IT, we can see all around a lot of projects that could easily be classified into the category of luxury applications.
From a leadership point of view, I think that going forward, we will see much more mature budgets which take into account what is really needed. World leaders would have to encourage global trade and try to create a niche in certain segments. This would come through experience gained after carefully investing time and resources in processes that have the potential and the power to hold and drive the economy forward on a global scale. This also means that countries which would be smart and understand that differences within themselves are good for nothing and just hurt their impression in the global market would be able to constantly make progress compared to countries which keep on grappling with their own issues. There would definitely is an issue of international responsibility but unless countries which need help don’t really make an effort to identify themselves as strategic players in the global economy, any amount of outside help that they will get is going to be useless because in a competitive world the only thing that drives progress is business interests and not charity.
Corporate leaders across the globe would have to reach a level of maturity where they can see and understand that not everything in this world starts as a million dollar project. The research and development departments of the organizations would have to be more focused on the needs of the organization and deliver more often and would have to work close to the production more than ever before. This way the companies would be able to ensure that they don’t spend on something without doing their “due diligence”: To make sure that they are not jumping in blind. This would help in bringing about a better transparency and accountability to processes since businesses would better understand the nature of how resources are tracked through a process.
From an individual point of view I see people becoming more aware of the global nature of the competition that they are facing. They should understand that a business would always try to make profits, granted that it should not be at the cost of quality. In a global market when the deliverable is something that takes anywhere from just a few milliseconds to a day be delivered from any part of the world to anywhere else on the face of this planet, giving a country specific preference to the people who do it not only becomes impractical but also something that’s not really profitable. Understanding these facts would help people bring up something in them which is at par with the global population that they are in line with to compete.
Weather it is focus on quality or innovation or it is the speed of development/production or the amount of data processed or the special attention on security or making sure that projects are delivered on time. These are the attributes of developing world ready products that will separate true talent from the rest. This really is what will guarantee job security for individuals and stability and survivability for the global market and the economy. It’s going to be a rough world out there and it will still be “survival of the fittest”.
Quote
Talking about LINQ to SQL: .NET Language-Integrated Query for Relational Data
It is important to notice two facts about the DataShape class:
- After assigning a DataShape to a DataContext, the DataShape cannot be modified. Any LoadWith or AssociateWith method call on such a DataShape will return an error at run time.
- It is impossible to create cycles by using LoadWith or AssociateWith. For example, the following generates an error at run time:
C#
DataShape ds = new DataShape();
ds.AssociateWith<Customer>(c=>c.Orders.Where(o=> o.Customer.Orders.Count() < 35));Visual Basic
Dim ds As DataShape = New DataShape()
ds.AssociateWith(Of Customer)(Function(cust As Customer) From ord In cust.Orders _
Where ord.Customer.Orders.Count() < 35))
It seems that not only has the DataShape class been changed to the DataLoadOptions.
However we see that
DataLoadOptions dlo = new DataLoadOptions();
dlo.AssociateWith<Customer>(c => c.Orders.Where(o => o.Customer.Orders.Count() < 35));
context.LoadOptions = dlo;
var q = from c in context.Customers
where c.City == "London"
select c;
foreach (Customer c in q)
{
Console.WriteLine("Customer id:{0}", c.CustomerID);
foreach (Order o in c.Orders)
{
Console.WriteLine("\tOrder id:{0}", o.OrderID);
}
}
Quote
If we look at the DataLoadOptions Class page on msdn we will find more explanation on how it works is found.
Rules
Note the following rules regarding DataLoadOptions usage:
Assigning a DataLoadOptions to a DataContext after the first query has been executed generates an exception.
Modifying a DataLoadOptions after it has been assigned to a DataContext generates an exception
Cycle Handling
LoadWith and AssociateWith directives must not create cycles. The following represent examples of such graphs:
Example 1: Self recursive
dlo.LoadWith<Employee>(e => e.Reports);
Example 2: Back-pointers
dlo.LoadWith <Customer>(c => C.Orders);
dlo.LoadWith <Order>(o => o.Customer);
Example 3: Longer cycles
Although this should not occur in a well-normalized model, it is possible.
dlo.LoadWith <A>(a => a.Bs);
dlo.LoadWith <B>(b => b.Cs);
dlo.LoadWith <C>(c => c.As);
Example 4: Self recursive subQueries
dlo.AssociateWith<A>(a=>a.As.Where(a=>a.Id=33));
Example 5: Longer recursive subqueries
dlo.AssociateWith<A>(a=>a.Bs.Where(b=>b.Id==3));
dlo.AssociateWith<B>(b=>b.As.Where(a=>a.Id==3));
The following are some general rules that help you understand what occurs in these scenarios.
LoadWith Each call to LoadWith checks whether cycles have been introduced into the graph. If there are, as in Examples 1, 2, and 3, an exception is thrown.
AssociateWith The engine at run time does not apply the existing SubQuery clauses to the relationship inside the expression.
In Example 4, the Where clause is executed against all A, not just the ones sub-filtered by the SubQuery expression itself (because that would be recursive)
In Example 5, the first Where clause is applied to all the Bs, even though there are subqueries on B. The second Where clause is applied to all the As even though there are subqueries on A.
The following statement runs correctly since it does not introduce any cycles.
dlo.LoadWith<Customer>(c => c.Orders);
However the following statement throws up a runtime invalid operation exception saying, “Cycles not allowed in LoadOptions LoadWith type graph”.
dlo.LoadWith<Customer>(c => c.Orders);
dlo.LoadWith<Order>(o => o.Customer);
But in the statement
ds.AssociateWith<Customer>(c=>c.Orders.Where(o=> o.Customer.Orders.Count() < 35));
seems to be working just fine as expected. It places a filter so that only those orders are selected where the total number of orders for a customer is less than 35. If we change it to say 4 then it will only select orders for those customers who have number of orders less than 4. Don’t really know why this might be though since this should have thrown an error.
Posts
All Comments
