Search Results

Search found 98173 results on 3927 pages for 'maintaining old code'.

facebook twitter digg google delicious technorati stumbleupon myspace wordpress linkedin gmail igoogle windows live tumblr viadeo yahoo buzz yahoo mail yahoo bookmarks favorites email print

Page 671/3927 | < Previous Page | 667 668 669 670 671 672 673 674 675 676 677 678  | Next Page >

  • SEO Checklist - Top 10 Most Common SEO Issues

    I read a lot of SEO blogs and forums and it never fails to amaze me how the same, fundamental basic SEO questions crop up time and time again, and the same old advice is wheeled out, rinsed, and then wheeled out again. And then when that is finished, it is wheeled out again for good measure. So, I thought I would compile the 10 most common SEO questions, and issues we come up against when assessing client's websites.

    Read the article

  • Which version of Debian are Ubuntu LTS releases based on?

    - by barnac1e
    This answer says: The base of the operating system, Debian, comes in three versions: Stable, Testing and Unstable. Normally, Ubuntu is based on Testing; the LTS releases are based on Stable. That cannot be true then for 12.04 because Debian Stable (Squeeze) is almost going to be old-stable, and it's obvious that the kernel versions in 12.04, packages, etc. cannot have come from Debian Squeeze. So then what other Debian Stable is there for Precise to be based on?

    Read the article

  • La mise à jour du projet Cloud OpenStack est disponible avec de nouvelles fonctionnalités et la participation de Cisco et Canonical

    La seconde mise à jour du code source de OpenStack est disponible avec de nouvelles fonctionnalités et la participation de Cisco et Canonical Mise à jour du 04/02/11, par Hinault Romaric La communauté OpenStack vient de dévoiler la seconde mise à jour de son projet open-source Cloud OpenStack dont le code source a été baptisé « Besack ». Pour mémoire OpenStack est un projet initié par la compagnie RackSpace en partenariat avec plusieurs compagnies parmi lesquelles la Nasa et Microsoft (lire ci-avant). La seconde mise à jour du projet inclut de nouvelles technologies de stockage, une prise en charge d'IPv6 et ...

    Read the article

  • Release Notes 12/12/2012

    This past week the CodePlex team worked on several fixes to improve the stability of our TFS infrastructure, including applying TFS 2012 Update 1. We apologize for the recent downtime. We are not completely out of the woods, but we appreciate your patience as we work through the issues. Additional Bug Fixes: Fixed several issues with character encoding within file paths. Fixed issue where the number of pull requests and forks were disappearing after selecting either link. Fixed issue blocking license changes when special characters exist in copyright holder field. Have ideas on how to improve CodePlex? Please visit our suggestions page! Vote for existing ideas or submit a new one. As always you can reach out to the CodePlex team on Twitter @codeplex or reach me directly @mgroves84

    Read the article

  • Silverlight 4: Printing Functionality

    Silverlight 4 now supports printing functionality using the Printing APIs. Using the API’s you can now print your whole application screen or a portion of the application. Also, you can customize the look while you printing your part/full application. In this post I will step you guys to the depth.

    Read the article

  • Painless management of a logging table in SQL Server

    Tables that log a record of what happens in an application can get very large, easpecially if they're growing by half a billion rows a day. You'll very soon need to devise a scheduled routine to remove old records, but the DELETE statement just isn't a realistic option with that volume of data. Hugo Kornelis explains a pain-free technique for SQL Server. Top 5 hard-earned Lessons of a DBA New! Part 4, ‘Disturbing Development’ by Grant Fritchey, features the return of Joe Deebeeay and a server-threatening encounter with ORMs - read it here

    Read the article

  • Tip: Regularily reset SharePoint Timer Service during development

    - by panjkov
    There is an interesting issue that can occur on development machines during development of SharePoint solutions that contain Site Templates or list templates in certain scenarios when site creation is not done manually, but using some kind of Custom Timer Job. The issue manifests in a way that even after retraction of old WSP and deployment of new WSP, even after performing IISRESET, sites created with new WSP don't have applied latest changes which are part of new WSP, but instead use (contain)...(read more)

    Read the article

  • Why C++ people loves multithreading when it comes to performances?

    - by user1849534
    I have a question, it's about why programmers seems to love concurrency and multi-threaded programs in general. I'm considering 2 main approach here: an async approach basically based on signals, or just an async approach as called by many papers and languages like the new C# 5.0 for example, and a "companion thread" that maanges the policy of your pipeline a concurrent approach or multi-threading approach I will just say that I'm thinking about the hardware here and the worst case scenario, and I have tested this 2 paradigms myself, the async paradigm is a winner at the point that I don't get why people 90% of the time talk about concurrency when they wont to speed up things or make a good use of their resources. I have tested multi-threaded programs and async program on an old machine with an Intel quad-core that doesn't offer a memory controller inside the CPU, the memory is managed entirely by the motherboard, well in this case performances are horrible with a multi-threaded application, even a relatively low number of threads like 3-4-5 can be a problem, the application is unresponsive and is just slow and unpleasant. A good async approach is, on the other hand, probably not faster but it's not worst either, my application just waits for the result and doesn't hangs, it's responsive and there is a much better scaling going on. I have also discovered that a context change in the threading world it's not that cheap in real world scenario, it's infact quite expensive especially when you have more than 2 threads that need to cycle and swap among each other to be computed. On modern CPUs the situation it's not really that different, the memory controller it's integrated but my point is that an x86 CPUs is basically a serial machine and the memory controller works the same way as with the old machine with an external memory controller on the motherboard. The context switch is still a relevant cost in my application and the fact that the memory controller it's integrated or that the newer CPU have more than 2 core it's not bargain for me. For what i have experienced the concurrent approach is good in theory but not that good in practice, with the memory model imposed by the hardware, it's hard to make a good use of this paradigm, also it introduces a lot of issues ranging from the use of my data structures to the join of multiple threads. Also both paradigms do not offer any security abut when the task or the job will be done in a certain point in time, making them really similar from a functional point of view. According to the X86 memory model, why the majority of people suggest to use concurrency with C++ and not just an async aproach ? Also why not considering the worst case scenario of a computer where the context switch is probably more expensive than the computation itself ?

    Read the article

facebook twitter digg google delicious technorati stumbleupon myspace wordpress linkedin gmail igoogle windows live tumblr viadeo yahoo buzz yahoo mail yahoo bookmarks favorites email print

< Previous Page | 667 668 669 670 671 672 673 674 675 676 677 678  | Next Page >