97 cosas que los programadores deberían saber

http://programmer.97things.oreilly.com/wiki/index.php/Contributions_Appearing_in_the_Book

"La belleza esta en lo simple", "La regla del boy scout" (dejar todo mejor que como lo encontraste), comenta solo lo que el codigo no puede decir por si mismo, 

Para arrancar una Pc desde usb (pen drive)

YUMI

Este soft permite poner las imagenes (.iso) en el pendrive y elegir con cual arrancar:

http://www.pendrivelinux.com/yumi-multiboot-usb-creator/


Para descargar las imagenes (.iso) de los sistemas operativos:

http://www.allbootdisks.com/download/iso.html

Genexus Tips

Si obtienen un mensaje como el siguiente al arrancar genexus y abriendo la kb "a network related or instance specific error occurred while establishing a connection to sql server". Hasta recien genexus abria el modelo lo mas tranquilo. 
Antes de desesperar y buscar en google la solucion magica (que no va a ayudar ya que es un mensaje generico de conexion con el sql server) vean simplemente si el servicio esta corriendo..

Genexus Evolution 2 - Windows 7 - Sqlexpress 2008

La idea era la siguiente: en una maquina en que uno desarrolla, a veces no tenemos acceso a un motor de base de datos adicional, en ese caso es conveniente utilizar el sqlexpress instalado como requisito para Genexus 2.

Este post, tal vez no sea muy riguroso ni muy preciso, pero lo publico como recordatorio para mi, y si a alguien le ahorra aunque sea media hora de busquedas y de intentos para hacer funcionar estas dos tecnologias juntas, estoy contento.

Cuando lo hice hace un par de años la tecnologia era un poco distinta (windows xp - evolution 1 - sqlexpress 2005), igual costo un poco, pero con estas nuevas versiones, costo mucho mas que la vez pasada.

Primero instale el sqlexpress2008 que descargue de la pagina de microsoft, version de 64 bits en español (Alto!, Si lo van a hacer, por favor descarguen la que viene con el management studio, se llama sqlexpress advance).

Instale genexus, y cuando termine de instalar, automaticamente busca la instancia de sql y crea las bases que necesita. 

Hasta ahi no habria ningun problema. Ahora bien, cuando uno trata de hacer una KB que apunte al sql es otro tema.

Hice muchas pruebas, intentos, configuraciones, googleos, pero no lograba que la aplicacion acceda al sqlexpress. Desde un gestor de sql podia acceder sin problemas.

 Lo unico que no pude resolver elegantemente, era instalar el management studio despues de haber instalado el sqlexpress. La unica manera que encontre fue instalar el sqlexpress advance y decirle que cree una nueva instancia con las herramientas de administracion basicas.

Hay dos cosas fundamentales que no estoy mencionando, la primera es decirle al sqlexpress que acepte conexiones por tcp/ip con el administrador de configuracion de sql server (en el 2005 estaba en otro lado pero es mas o menos parecido) y la segunda es: si van a desarrollar con java, el driver jdbc de sql de microsoft parece que estuviera incluido en genexus, pero no.

Mucho de los mensajes que obtenia era "No suitable driver" lo que a mi me parecia un mensaje erroneo, si genexus incluye los drivers. 

Copie el sqljdbc4.jar (que lo tenia de antes, supongo que si se googlea se encuentra) a la carpeta gxjava\drivers dentro de la instalacion de genexus, y lo agregue al classpath.

Tambien agregue una regla en el firewall pero no estoy seguro que esto sea estrictamente necesario. Y lo que recomiendo es que si hacen cambios y no notan que cambie nada, cierren genexus y vuelvan abrirlo y lo mismo para el sql. Lo digo porque cambie la configuracion en el sql y no la tomo, y empezo a funcionar sin tocar nada, lo unico que hice fue reiniciar la pc.

Trucos - Troubleshooting Windows XP

http://www.kellys-korner-xp.com/xp.htm

Conversor video - Modelador de Hogares

Conversor online de videos de youtube (o cualquier otra pagina) y permite cambiar tamaño, bitrate o hasta elegir una parte del video

http://www.online-convert.com

Modelador de Casas (autodesk) como el 3d-home y otros (Muy facil de usar)

www.homestyler.com

5 formas de enviar archivos grandes

5 formas de enviar archivos grandes

http://www.genbeta.com/web/cinco-servicios-para-enviar-grandes-archivos-de-forma-comoda

Antivirus on line

Funciona sin instalacion como el active scan de panda software

http://housecall.trendmicro.com/es/

Como acceder a sqlexpress mediante cliente de sql

FAQ: How to connect to SQL Express from "downlevel clients"(Access 2003, VS 2003, VB 6, etc(basically anything that is not using .Net 2.0 or the new SQL Native Client))

 sqlexpress 23 Jul 2004 1:09 AM 35

This is the short version, the longer version is further down, also make sure and review the SQL Express BOL and the Mini BOL.

Follow these steps:

1. Make sure express is running correctly (assumes a default install)

 Drop to a cmd prompt

 Type the following

        sqlcmd -S.\sqlexpress

 You should get a prompt like this

        1>

 Type

        Exit

 to exit sqlcmd

2. Enable Protocols

     a. Launch SQL Computer Manager

     b. Expand "Server Network Configuration"

     c. Expand Protocols for "SQLEXPRESS"

     d. Enable Np (for local and remote access)

     e. Enable TCP (for local and remote access)

3. Restart SQL Express

     a. can be done from either SQL Computer Manager, Services applet, or command line( net start mssql$sqlexpress)

4. Start SQL Browser service from Service applet or command line( net start sqlbrowser)

At this point the client should be able to connect, if the machine is rebooted then the last step (4) needs to be repeated as this service must always be running. You can also set this service to autostart via Computer Manager, Services Management Applet.

These actions need to be performed wherever the machine is that has SQL Server Express running on it. If machine A is running SQL Express and an attempt is made to connect from a local tool or applet the steps must be performed on machine A. If an attempt is made to connect from a different machine(B) then the steps still need to be performed on Machine A.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The long version.

This entry is designed to help explain the reasons behind the steps in the short version of this post. Lets walk through the steps and the problems and try and explain whats happening

Checking to make sure that Express is running via SQLCMD

The default install for SQL Express installs Express as a named instance(called SQLExpress), with no network listening and with Windows Authentication support only.

To connect to a named instance of SQL Server the convention is to use a servername of the format <servername>\<instancename>, its also possible to shortcut the machinename to either "." or "(local)"(these shortcuts work with all protocols, localhost will also work but only with TCP/IP in older clients,however SQL Native Access supports resolution of LocalHost for Named Pipes and Shared Memory).

No user id and password has been specified because of the default windows authentication, if the install had been changed to specify mixed mode authentication and a password had been given then this could have been used.

Enabling Protocols

Because SQL Server Express does not listen on the network by default connections are made using a local protocol, in the case of the VS 2005 SKUs this is the shared memory protocol. The interface to this has changed in SQL Server 2005 such that older clients can no longer use it. Hence for older clients to work a different local protocol or a network protocol must be used, these are not enabled by default and must be manually enabled.

SQL Browser Service

In general when a client connects remotely to a SQL Server named instance the client does not know the port that the instance is listening on(you can work around this by configuring SQL Server named instances to listen on a specific port and then specifying that port in the connection string in the format <servername>,<port number>)

So when an application attempts to connect to a named instance in the form <servername>\<instancename> the client connection needs to be directed to the correct port. In SQL Server 2000 one of the running services had a built in listener that received the named instance connection requests and redirected them appropriately.

In SQL Server 2005 this functionality has been moved to a dedicated listener service, that service is SQLBrowser.

SQLBrowser also performs another service, that of SQL Server Discovery, its common in many UIs from Microsoft and others to have the ability to browse for instances of SQL Server running locally or remotely, again in SQL Server 2000 this was handled by one of the running instances of SQL Server, in SQL Server 2005 this is handled by the SQLBrowser Service.

Thus the SQLBrowser Service must be started to be able to discover any instance on the machine, and also to connect to named instances through protocols other than shared memory. If network protocols are not enabled via the setup switch then the browser service is not set to autostart.

SQL Native Client

SQL Server native connectivity is defined as connectivity through OLE DB(ADO uses OLE DB under the covers) or ODBC means in SQL Server 2005 (dblib is not an included as a data access technology in SQL Server 2005).

In previous releases of SQL Server(SQL7 and SQL2000) an update to MDAC was preferred for client apps, this means the installation of an entire MDAC update for SQL Server connectivity. In SQL Server 2005 we no longer require an MDAC update as we have refactored out the SQL Server specific connectivity components for OLE DB and ODBC.

As such in SQL Server 2005 no MDAC update is required to connect(although MDAC 2.8 is preferred, any MDAC from Windows 2000 SP3 upwards is supported), but a new component is required. This component is referred to as SQL Native Access.

These components include support for OLE DB and ODBC accessed through a single .dll called: SQLNCLI.dll, this file and its support  files are redistributable.

SQL Native Client is NOT required for managed data access via .Net APIs.

 

-Euan Garden

Product Unit Manager

SQL Server Tools

fuente:http://blogs.msdn.com/b/sqlexpress/archive/2004/07/23/192044.aspx

http://docs.aquafold.com/ads/4.7/screenshots/docs/express-register.gif

ojo: poner como direccion de host: 127.0.0.1\SQLExpress y el port por default:1433

Cursos de Genexus

Con ejemplos y pdfs

 http://training.genexus.com/cursos/todos-los-cursos?es