samuraiprogrammer.com Report : Visit Site

Technical data of the samuraiprogrammer.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host samuraiprogrammer.com. Currently, hosted in United States and its service provider is Lunar Pages .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Microsoft-IIS/8.5 containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

home | about me | developer pfe blog | become a developer pfe i know kung fu contact email me follow me | | email me follow me | | -- categories .net .net 4 .net upgrade access database asp.net azure best practice bing c# code reviews database development google hiring iis life linq logging microsoft online translator openxml parallel perfmon performance pivot powerpoint powershell premier field engineer (pfe) presentations productivity regex scripting security troubleshooting vba wcf on this page pinvoke error in .net 4: array size control parameter index is out of range getting more information from the word error box when troubleshooting openxml / wordml issues the (potentially) dark side of parallelism… yield return…a little known but incredible language feature linking your pivot collections the fun and easy way pivoting asp.net event log error messages visualizing azure performance counters… don’t guess when it comes to performance…a regex story. optimizing your life: e-mail edition exposing any class as a wcf endpoint… archive november, 2011 (1) september, 2011 (1) december, 2010 (1) october, 2010 (3) september, 2010 (4) august, 2010 (8) july, 2010 (12) blogroll coding 4 fun david hayden debugging toolbox eric j smith girl developer internet explorer team blog jesse liberty joel on software maoni's weblog mike stall's .net debugging blog patrick dussud pfe - developer notes for the field rico mariani scott hanselman scottgu's blog tess ferrandez vance morrison's weblog disclaimer the opinions expressed herein are my own personal opinions and do not represent my employer's view in any way. sign in are you ready for your next challenge? site update july 2010 - (aka - where are all of your posts?) latest tweet: saturday, 19 november 2011 pinvoke error in .net 4: array size control parameter index is out of range saturday, 19 november 2011 07:45:14 (central standard time, utc-06:00) ( .net 4 | perfmon | performance ) so in a code-base i was working in yesterday, we use pinvoke to call out to the performance data helper (pdh) api’s to collect performance information for machines without using perfmon. one of those pinvoke calls looked like this: /* pdh_status pdhexpandcounterpath( lpctstr szwildcardpath, lptstr mszexpandedpathlist, lpdword pcchpathlistlength ); */ [dllimport("pdh.dll", charset = charset.unicode)] private static extern pdhstatus pdhexpandcounterpath( string szwildcardpath, [marshalas(unmanagedtype.lparray, sizeparamindex = 3)] char[] mszexpandedpathlist, ref uint pcchpathlistlength ); in .net 3.5 and below, this pinvoke call works perfectly fine. in .net 4.0, though, i saw this exception: system.runtime.interopservices.marshaldirectiveexception: cannot marshal 'parameter #2': array size control parameter index is out of range. at system.runtime.interopservices.marshal.internalprelink(iruntimemethodinfo m) at system.runtime.interopservices.marshal.prelink(methodinfo m) so, can you identify what’s wrong in the code above? well, the array size control parameter index indicates the zero-based parameter that contains the count of the array elements, similar to size_is in com. because the marshaler cannot determine the size of an unmanaged array, you have to pass it in as a separate parameter. so in the call above, parameter #2, we specify “sizeparamindex = 3” to reference the pcchpathlistlength parameter to set the length of the array. so what’s the catch? well, since the sizeparamindex is a zero-based index, the 3rd parameter doesn’t really exist. so, to fix this, we just change the “sizeparamindex=3” to “sizeparamindex=2” to reference the pcchpathlistlength: /* pdh_status pdhexpandcounterpath( lpctstr szwildcardpath, lptstr mszexpandedpathlist, lpdword pcchpathlistlength ); */ [dllimport("pdh.dll", charset = charset.unicode)] private static extern pdhstatus pdhexpandcounterpath( string szwildcardpath, [marshalas(unmanagedtype.lparray, sizeparamindex = 2)] char[] mszexpandedpathlist, ref uint pcchpathlistlength ); it looks like in .net 3.5 and below, though, we allowed you to reference either 1-based index or a zero-based index but in .net 4.0, we buttoned that up a bit and force you to use the zero-based index. big thanks to my co-worker and frequent collaborator, zach kramer for his assistance in looking at this issue. until next time! comments [0] | trackback | saturday, 03 september 2011 getting more information from the word error box when troubleshooting openxml / wordml issues saturday, 03 september 2011 11:56:55 (central daylight time, utc-05:00) ( openxml | troubleshooting ) so, many apologies for dropping off the face of the blogosphere lately. fortunately (or unfortunately, depending on your perspective), i’ve been really busy at work. i’ve been working on some really cool things that i hope i’ll be able to talk about publicly soon. for now, though, i wanted to pass on something that i haven’t seen documented in other places that actually helped me quite a bit lately. so, for those of you that generate word documents via the openxml (or any other of a variety of methods), you may have come across something like this when you opened up a document you just generated: there are some problems with this message but the big one is that it just says “line: 1, column: 0”. not exactly a map to the error. as a result, you may have stared at this message for a long time and wondered – “how the heck do i fix this? what is the real problem?”. well, let me show you a really quick and easy way of getting more information than what is initially provided. step 1: change the extension from docx to zip as you may or may not know, all openxml documents (or office documents since office 2007) are actually zip files at their core. that means you can just crack them open and peer inside. see the difference? easy! step 2: extract the zip file to a folder once again, pretty straight forward. once you extract the zip file above, you should see a structure like the following: now, from here – you’ll be able to locate the file referenced in that cryptic error message above. step 3: find the file that’s causing the problem in the example above, the message states that the problem lies with the file “/word/document.xml” so just navigate to the “word” folder and find the “document.xml”. step 4: open and format the file in visual studio one of the great features of visual studio is that it can format an xml file for you. so, in our case, the document.xml file is natively just one big line: incidentally, this is why the message always states “line 1,…” in the error message. as far as word is concerned, the problem is on the first line. fortunately for us, though, word can take that single line file and format it for us. just use the edit > advanced > format document option in visual studio: that will then format the xml and make it look closer to: step 5: recreate the word doc and get the additional information now that you have the file formatted appropriately, you can just re-create the word document and re-open it. for this, just go back to the root of the document, select all the files/folders and then zip it back up: once it’s zipped back up again, just change the extension from zip to docx and re-open the file. when you do so, you’ll see the following: note that now, you’ll see that it says “line: 5667, column: 0” – which will point to the exact line causing the problem – which allows you to just go back to the “document.xml” file you already have open in visual studio to see the problem. in our case: note that this won’t magically fix your problem. you’ll still need to examine the wordml to figure out the problem – but at least you know where to go. and knowing is half the battle! that’s all for now and i will be back with some more developer stuff soon. until next time! comments [0] | trackback | sunday, 05 december 2010 the (potentially) dark side of parallelism… sunday, 05 december 2010 12:52:17 (central standard time, utc-06:00) ( .net 4 |

URL analysis for samuraiprogrammer.com

http://www.samuraiprogrammer.com/blog/commentview,guid,a7f8712d-020c-4cd3-acf3-8342ddc1e629.aspx#commentstart
http://www.samuraiprogrammer.com/blog/2010/07/29/areyoureadyforyournextchallengewerehiring.aspx
http://www.samuraiprogrammer.com/blog/ct.ashx?id=e4740c06-15bc-4ad7-a99a-735725fb5f1c&url=http%3a%2f%2fwww.samuraiprogrammer.com%2fblog%2fcontent%2fbinary%2fwindows-live-writer%2f9b44f80892c4_9194%2fimage_18.png
http://www.samuraiprogrammer.com/blog/2010/10/17/yieldreturnalittleknownbutincrediblelanguagefeature.aspx
http://www.samuraiprogrammer.com/blog/categoryview,category,powerpoint.aspx
http://www.samuraiprogrammer.com/blog/categoryview,category,database.aspx
http://www.samuraiprogrammer.com/blog/trackback.aspx?guid=56e41ecc-3924-42fd-984c-064d51da2cce
http://www.samuraiprogrammer.com/blog/syndicationservice.asmx/getrsscategory?categoryname=linq
http://www.samuraiprogrammer.com/blog/syndicationservice.asmx/getrsscategory?categoryname=c%23
http://www.samuraiprogrammer.com/blog/ct.ashx?id=3acb3cdd-ccc7-4e87-a812-da7b080682a6&url=http%3a%2f%2fwww.samuraiprogrammer.com%2fblog%2fcontent%2fbinary%2fwindows-live-writer%2f67a06ba55268_8dea%2fimage_12.png
http://www.samuraiprogrammer.com/blog/syndicationservice.asmx/getrsscategory?categoryname=life
http://www.samuraiprogrammer.com/blog/syndicationservice.asmx/getrsscategory?categoryname=scripting
http://www.samuraiprogrammer.com/blog/ct.ashx?id=e4740c06-15bc-4ad7-a99a-735725fb5f1c&url=http%3a%2f%2fwww.samuraiprogrammer.com%2fblog%2fcontent%2fbinary%2fwindows-live-writer%2f9b44f80892c4_9194%2fimage_6.png
http://www.samuraiprogrammer.com/blog/ct.ashx?id=90aee052-b425-4e42-82ee-2b736c506e39&url=http%3a%2f%2fwww.samuraiprogrammer.com%2fblog%2fcontent%2fbinary%2fwindows-live-writer%2fdf4a939434b1_cb17%2f__gregvar-pc_asp_netv4_0_30319_requestsqueued_2.gif
http://www.samuraiprogrammer.com/blog/ct.ashx?id=3acb3cdd-ccc7-4e87-a812-da7b080682a6&url=http%3a%2f%2fblogs.msdn.com%2fb%2fdevelopertofu%2f

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: SAMURAIPROGRAMMER.COM
Registry Domain ID: 545595996_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://www.tucowsdomains.com
Updated Date: 2018-07-24T08:00:39Z
Creation Date: 2006-08-07T18:36:40Z
Registry Expiry Date: 2019-08-07T18:36:40Z
Registrar: Tucows Domains Inc.
Registrar IANA ID: 69
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: ok https://icann.org/epp#ok
Name Server: NS7.LUNARBREEZE.COM
Name Server: NS8.LUNARBREEZE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-07-28T08:47:07Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR Tucows Domains Inc.

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =samuraiprogrammer.com

  PORT 43

  TYPE domain

DOMAIN

  NAME samuraiprogrammer.com

  CHANGED 2018-07-24

  CREATED 2006-08-07

STATUS
ok https://icann.org/epp#ok

NSERVER

  NS7.LUNARBREEZE.COM 74.50.26.198

  NS8.LUNARBREEZE.COM 74.50.26.199

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .