Hi,
Yesterday I started an idea that came to my mind in my trips: create an Infopath form to generate a BDC file (Application definition). The first version (v0.1) that you can download has room for improvement (coming soon :)) and It can generate only model (not resources).
The most challenging node was the TypeDescriptor, as it is a repeating recursive section (and first I forgot to clear the compatibility with forms server ;) [this control cannot be used in browser mode]) and Infopath does not represent correctly without manual action.
Thanks to Nick Dallett !
Please send me examples generated with the tool and bugs!:
Screenshoot of the tool
Cheers!
BDC
Web is changing (really? :) when ;)) you can check more and more web sites changing to a new look at microsoft. Maybe one day others will do too.
See http://www.microsoft.com/silverlight/ or http://www.microsoft.com/ or http://www.microsoft.com/design/Culture/Master.aspx and on the other hand http://www.microsoft.com/windowsvista/ or http://office.microsoft.com/
new clean, easy to find and easy to navigate sites but including new 'feeling'.
Yes others Corp have changed, but in my opinion they have upgraded the technology, not a rework of the concept
Check http://www.archive.org/web/web.php for some examples.
Maybe, this is something Microsoft Office SharePoint Server 2007 is going to accelerate:
Go for it!
Here again!.
Last year I have been pretty busy with many MOSS projects, so I will start again with SharePoint Technologies :)
As I usually create VPC, I end up with different customer demo machines. Today I wanted to use one of them, but I thought if it was possible to change domain name/computer name in order to map other customer name.
My environment was a Single Server install (DC+Standalone server:Windows R2 2003 Server) of MOSS 2007 with english+spanish language pack.
The steps I followed were:
Finally, I wanted to change the computer name. So I used netdom tool http://technet2.microsoft.com/WindowsServer/en/library/460e3705-9e5d-4f9b-a139-44341090cfd41033.mspx?mfr=true
As the server had DNS Service, a change in the configure entries was necessary too (including a FQDN that resolves to the server).
After this changes, I needed to change:
P.S.
If you somehow run /clean before doing the gpfixup, you can use the GPMC http://www.microsoft.com/windowsserver2003/gpmc/default.mspx to fix the problem.
Delete the link pointing to the old domain and create a new one (Linked Group Policy Objects)
[I tried the other steps in a VPC, and didn't work, so I tried the dcgpofix tool too and reboot with this in mind]
MOSS, VPC, DC, GPMC, SSP