It's your turn! As the interview comes to a close, one of the final questions you may be asked is "What can I answer for you?" Have interview questions of your own ready to ask. You aren't simply trying to get this job - you are also interviewing the employer to assess whether this company and the position are a good fit for you. Here are questions to ask the interviewer so you can ensure the company is a good match for your qualifications and interests. How would you describe the responsibilities of the position? How would you describe a typical week/day in this position? Is this a new position? If not, what did the previous employee go on to do? What is the company's management style? Who does this position report to? If I am offered the position, can I meet him/her? How many people work in this office/department? How much travel is expected? Is relocation a possibility? What is the typical work week? Is overtime expected? What are the prospects for growth and a...
The 1st question comes to my mind when I hear about another new webserver like IIS for .NET applications. Why do we need this new webserver called 'Kestrel'? As we all know Asp.Net Core is primarily to make Asp.Net Core applications to run across multiple platforms (Windows/Unix/Linux/MAC OS). Even though we have IIS with rich in features but mostly used webserver for Windows OS only. Each webserver has a different configurations expected to startup and Kestrel will make Asp.Net Core applications have different Startup mechanisms. This is why Asp.Net Core applications use Kestrel webserver as an in-process server where the application will have same and consistent Startup (Main() and Startup.ConfigireServices() & Startup.Configure()) process even when offering cross platform support. Kestrel is an open source, cross platform, light weight and a default webserver used for Asp.Net Core applications. Asp.Net Core applications run Kestrel webserver as in-process server to ...
ets write a simple query to fetch the top 20 employees from the Northwind database and count the number of orders placed by each employee. NORTHWNDEntities context = new NORTHWNDEntities(); var employees = context.Employees.Take(20).ToList(); foreach (Employee employee in employees) { Console.WriteLine("Total number of order by employee : {0}", employee.Orders.Count); } We start off with creating the ObjectContext which is NORTHWNDEntities in our case. We filter the 20 employees using Take method on the employees entity collection. Then we loop over the individual employees and display the count of Orders to the console window. By default Entity Framework 4 enables the Lazy Loading feature. Because of this there are multiple hits to the database server. The initial query which filters the 20 employees is executed when we start iterating over the loop. And then for each employee a separate query i...
Comments
WCF Training | WCF Online Training | Online WCF Training | WCF Training in chennai | Dot Net Training Institutes in Chennai | Dot Net Training in Chennai | Online Dot Net Training